Resource conflict

ABSTRACT

A wireless device may receive one or more radio resource control (RRC) messages comprising first parameters of a first configured grant configuration of the cell and second parameters of a second configured grant configuration of the cell. The wireless device may trigger a power headroom report. The wireless device may determine one of: a first resource associated with the first configured grant configuration; and a second resource associated with the second configured grant configuration, as a selected uplink resource for transmitting the power headroom report. The wireless device may determine the selected uplink resource based on a first priority of the first configured grant configuration and a second priority of the second configured grant configuration. The first resource and the second resource may overlap in one or more symbols. The wireless device may transmit the power headroom report via the selected uplink resource.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/842,154, filed May 2, 2019, which is hereby incorporated by referencein its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per anaspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as peran aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stationsas per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals as per an aspect of an embodiment of the presentdisclosure.

FIG. 5B is a diagram of an example downlink channel mapping and exampledownlink physical signals as per an aspect of an embodiment of thepresent disclosure.

FIG. 6 is a diagram depicting an example frame structure as per anaspect of an embodiment of the present disclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDMsubcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS blocktransmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam managementprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of anembodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity asper an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per anaspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of anembodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 15 is an example Single Entry PHR format as per an aspect of anembodiment of the present disclosure.

FIG. 16 is an example table for PHR calculation as per an aspect of anembodiment of the present disclosure.

FIG. 17 is an example table for PHR calculation as per an aspect of anembodiment of the present disclosure.

FIG. 18 is an example table for PHR calculation as per an aspect of anembodiment of the present disclosure.

FIG. 19 is an example Multiple Entry PHR format as per an aspect of anembodiment of the present disclosure.

FIG. 20 is an example Multiple Entry PHR format as per an aspect of anembodiment of the present disclosure.

FIG. 21 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 22 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 23 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 24 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 25 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 26 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 27 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 28 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 29 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 30 is an example procedure as per an aspect of an embodiment of thepresent disclosure.

FIG. 31 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable handling resourceconflict. Embodiments of the technology disclosed herein may be employedin the technical field of multicarrier communication systems. Moreparticularly, the embodiments of the technology disclosed herein mayrelate to resource conflict handling in multicarrier communicationsystems.

The following Acronyms are used throughout the present disclosure:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BPSK Binary Phase Shift Keying

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CN Core Network

CP Cyclic Prefix

CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control CHannel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic CHannel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolved-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCID Logical Channel IDentifier

LTE Long Term Evolution

MAC Media Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node

NACK Negative Acknowledgement

NAS Non-Access Stratum

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-eNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NR PDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM Orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PMI Precoding Matrix Indicator

PRACH Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank Indicator

RLC Radio Link Control

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SC-FDMA Single Carrier-Frequency Division Multiple Access

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number

S-GW Serving GateWay

SI System Information

SIB System Information Block

SMF Session Management Function

SN Secondary Node

SpCell Special Cell

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSS Secondary Synchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance

TAG Timing Advance Group

TAI Tracking Area Identifier

TAT Time Alignment Timer

TB Transport Block

TC-RNTI Temporary Cell-Radio Network Temporary Identifier

TDD Time Division Duplex

TDMA Time Division Multiple Access

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared CHannel

UPF User Plane Function

UPGW User Plane Gateway

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CodeDivision Multiple Access (CDMA), Orthogonal Frequency Division MultipleAccess (OFDMA), Time Division Multiple Access (TDMA), Wavelettechnologies, and/or the like. Hybrid transmission mechanisms such asTDMA/CDMA, and OFDM/CDMA may also be employed. Various modulationschemes may be applied for signal transmission in the physical layer.Examples of modulation schemes include, but are not limited to: phase,amplitude, code, a combination of these, and/or the like. An exampleradio transmission method may implement Quadrature Amplitude Modulation(QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase ShiftKeying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, a RAN node may be a next generation Node B (gNB) (e.g.120A, 120B) providing New Radio (NR) user plane and control planeprotocol terminations towards a first wireless device (e.g. 110A). In anexample, a RAN node may be a next generation evolved Node B (ng-eNB)(e.g. 124A, 124B), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device (e.g. 110B). The first wireless device maycommunicate with a gNB over a Uu interface. The second wireless devicemay communicate with a ng-eNB over a Uu interface. In this disclosure,wireless device 110A and 110B are structurally similar to wirelessdevice 110. Base stations 120A and/or 120B may be structurally similarlyto base station 120. Base station 120 may comprise at least one of a gNB(e.g. 122A and/or 122B), ng-eNB (e.g. 124A and/or 124B), and or thelike.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of UEs inRRC_INACTIVE state, distribution function for Non-Access Stratum (NAS)messages, RAN sharing, and dual connectivity or tight interworkingbetween NR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may beinterconnected with each other by means of Xn interface. A gNB or anng-eNB may be connected by means of NG interfaces to 5G Core Network(5GC). In an example, 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may beconnected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g. non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer and/or warning message transmission, combinations thereof,and/or the like.

In an example, a UPF may host functions such as anchor point forintra-/inter-Radio Access Technology (RAT) mobility (when applicable),external PDU session point of interconnect to data network, packetrouting and forwarding, packet inspection and user plane part of policyrule enforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, QoS handling for user plane, e.g. packetfiltering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplinktraffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signalingtermination, NAS signaling security, Access Stratum (AS) securitycontrol, inter Core Network (CN) node signaling for mobility between3^(rd) Generation Partnership Project (3GPP) access networks, idle modeUE reachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (subscription and policies),support of network slicing and/or Session Management Function (SMF)selection.

FIG. 2A is an example user plane protocol stack, where Service DataAdaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers andPhysical (PHY) (e.g. 215 and 225) layer may be terminated in wirelessdevice (e.g. 110) and gNB (e.g. 120) on the network side. In an example,a PHY layer provides transport services to higher layers (e.g. MAC, RRC,etc.). In an example, services and functions of a MAC sublayer maycomprise mapping between logical channels and transport channels,multiplexing/demultiplexing of MAC Service Data Units (SDUs) belongingto one or different logical channels into/from Transport Blocks (TBs)delivered to/from the PHY layer, scheduling information reporting, errorcorrection through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between UEs by means of dynamic scheduling, priority handlingbetween logical channels of one UE by means of logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. In an example, mappingrestrictions in a logical channel prioritization may control whichnumerology and/or transmission timing a logical channel may use. In anexample, an RLC sublayer may supports transparent mode (TM),unacknowledged mode (UM) and acknowledged mode (AM) transmission modes.The RLC configuration may be per logical channel with no dependency onnumerologies and/or Transmission Time Interval (TTI) durations. In anexample, Automatic Repeat Request (ARQ) may operate on any of thenumerologies and/or TTI durations the logical channel is configuredwith. In an example, services and functions of the PDCP layer for theuser plane may comprise sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g. in case of split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. In an example, services andfunctions of SDAP may comprise mapping between a QoS flow and a dataradio bearer. In an example, services and functions of SDAP may comprisemapping Quality of Service Indicator (QFI) in DL and UL packets. In anexample, a protocol entity of SDAP may be configured for an individualPDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayersand PHY (e.g. 236 and 245) layer may be terminated in wireless device(e.g. 110) and gNB (e.g. 120) on a network side and perform service andfunctions described above. In an example, RRC (e.g. 232 and 241) may beterminated in a wireless device and a gNB on a network side. In anexample, services and functions of RRC may comprise broadcast of systeminformation related to AS and NAS, paging initiated by 5GC or RAN,establishment, maintenance and release of an RRC connection between theUE and RAN, security functions including key management, establishment,configuration, maintenance and release of Signaling Radio Bearers (SRBs)and Data Radio Bearers (DRBs), mobility functions, QoS managementfunctions, UE measurement reporting and control of the reporting,detection of and recovery from radio link failure, and/or NAS messagetransfer to/from NAS from/to a UE. In an example, NAS control protocol(e.g. 231 and 251) may be terminated in the wireless device and AMF(e.g. 130) on a network side and may perform functions such asauthentication, mobility management between a UE and a AMF for 3GPPaccess and non-3GPP access, and session management between a UE and aSMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logicalchannels for a wireless device. A logical channel in the plurality oflogical channels may correspond to a radio bearer and the radio bearermay be associated with a QoS requirement. In an example, a base stationmay configure a logical channel to be mapped to one or moreTTIs/numerologies in a plurality of TTIs/numerologies. The wirelessdevice may receive a Downlink Control Information (DCI) via PhysicalDownlink Control CHannel (PDCCH) indicating an uplink grant. In anexample, the uplink grant may be for a first TTI/numerology and mayindicate uplink resources for transmission of a transport block. Thebase station may configure each logical channel in the plurality oflogical channels with one or more parameters to be used by a logicalchannel prioritization procedure at the MAC layer of the wirelessdevice. The one or more parameters may comprise priority, prioritizedbit rate, etc. A logical channel in the plurality of logical channelsmay correspond to one or more buffers comprising data associated withthe logical channel. The logical channel prioritization procedure mayallocate the uplink resources to one or more first logical channels inthe plurality of logical channels and/or one or more MAC ControlElements (CEs). The one or more first logical channels may be mapped tothe first TTI/numerology. The MAC layer at the wireless device maymultiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logicalchannel) in a MAC PDU (e.g., transport block). In an example, the MACPDU may comprise a MAC header comprising a plurality of MAC sub-headers.A MAC sub-header in the plurality of MAC sub-headers may correspond to aMAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/orone or more MAC SDUs. In an example, a MAC CE or a logical channel maybe configured with a Logical Channel IDentifier (LCID). In an example,LCID for a logical channel or a MAC CE may be fixed/pre-configured. Inan example, LCID for a logical channel or MAC CE may be configured forthe wireless device by the base station. The MAC sub-headercorresponding to a MAC CE or a MAC SDU may comprise LCID associated withthe MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/orimpact one or more processes (e.g., set values of one or more parametersof the one or more processes or start and/or stop one or more timers ofthe one or more processes) at the wireless device by employing one ormore MAC commands. The one or more MAC commands may comprise one or moreMAC control elements. In an example, the one or more processes maycomprise activation and/or deactivation of PDCP packet duplication forone or more radio bearers. The base station may transmit a MAC CEcomprising one or more fields, the values of the fields indicatingactivation and/or deactivation of PDCP duplication for the one or moreradio bearers. In an example, the one or more processes may compriseChannel State Information (CSI) transmission of on one or more cells.The base station may transmit one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells. Inan example, the one or more processes may comprise activation ordeactivation of one or more secondary cells. In an example, the basestation may transmit a MA CE indicating activation or deactivation ofone or more secondary cells. In an example, the base station maytransmit one or more MAC CEs indicating starting and/or stopping one ormore Discontinuous Reception (DRX) timers at the wireless device. In anexample, the base station may transmit one or more MAC CEs indicatingone or more timing advance values for one or more Timing Advance Groups(TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, andbase station 2, 120B) and a wireless device 110. A wireless device maybe called an UE. A base station may be called a NB, eNB, gNB, and/orng-eNB. In an example, a wireless device and/or a base station may actas a relay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g. a wireless modem, an antenna, a wiredmodem, and/or the like), at least one processor 321A, and at least oneset of program code instructions 323A stored in non-transitory memory322A and executable by the at least one processor 321A. The base station2, 120B, may comprise at least one communication interface 320B, atleast one processor 321B, and at least one set of program codeinstructions 323B stored in non-transitory memory 322B and executable bythe at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may comprise many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At Radio Resource Control (RRC)connection establishment/re-establishment/handover, one serving cell mayprovide the NAS (non-access stratum) mobility information (e.g. TrackingArea Identifier (TAI)). At RRC connection re-establishment/handover, oneserving cell may provide the security input. This cell may be referredto as the Primary Cell (PCell). In the downlink, a carrier correspondingto the PCell may be a DL Primary Component Carrier (PCC), while in theuplink, a carrier may be an UL PCC. Depending on wireless devicecapabilities, Secondary Cells (SCells) may be configured to formtogether with a PCell a set of serving cells. In a downlink, a carriercorresponding to an SCell may be a downlink secondary component carrier(DL SCC), while in an uplink, a carrier may be an uplink secondarycomponent carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to one cell. The cell ID or cell index may alsoidentify the downlink carrier or uplink carrier of the cell (dependingon the context it is used). In the disclosure, a cell ID may be equallyreferred to a carrier ID, and a cell index may be referred to a carrierindex. In an implementation, a physical cell ID or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted on a downlink carrier. A cell index may be determinedusing RRC messages. For example, when the disclosure refers to a firstphysical cell ID for a first downlink carrier, the disclosure may meanthe first physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.When the disclosure indicates that a first carrier is activated, thespecification may equally mean that a cell comprising the first carrieris activated.

A base station may transmit to a wireless device one or more messages(e.g. RRC messages) comprising a plurality of configuration parametersfor one or more cells. One or more cells may comprise at least oneprimary cell and at least one secondary cell. In an example, an RRCmessage may be broadcasted or unicasted to the wireless device. In anexample, configuration parameters may comprise common parameters anddedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). Another SI maybe transmitted via SystemInformationBlockType2. For a wireless device inan RRC_Connected state, dedicated RRC signaling may be employed for therequest and delivery of the other SI. For the wireless device in theRRC_Idle state and/or the RRC_Inactive state, the request may trigger arandom-access procedure.

A wireless device may report its radio access capability informationwhich may be static. A base station may request what capabilities for awireless device to report based on band information. When allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference, or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection witha network. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition, and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. When adding a new SCell,dedicated RRC signaling may be employed to send all required systeminformation of the SCell i.e. while in connected mode, wireless devicesmay not need to acquire broadcasted system information directly from theSCells.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells and cell groups). As part of the RRCconnection reconfiguration procedure, NAS dedicated information may betransferred from the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be to establish (or reestablish, resume) an RRC connection. an RRCconnection establishment procedure may comprise SRB1 establishment. TheRRC connection establishment procedure may be used to transfer theinitial NAS dedicated information/message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure after successful security activation. Ameasurement report message may be employed to transmit measurementresults.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g. a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 stored in non-transitory memory 315 and executable bythe at least one processor 314. The wireless device 110 may furthercomprise at least one of at least one speaker/microphone 311, at leastone keypad 312, at least one display/touchpad 313, at least one powersource 317, at least one global positioning system (GPS) chipset 318,and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding/processing, data processing, powercontrol, input/output processing, and/or any other functionality thatmay enable the wireless device 110, the base station 1 120A and/or thebase station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to thespeaker/microphone 311, the keypad 312, and/or the display/touchpad 313.The processor 314 may receive user input data from and/or provide useroutput data to the speaker/microphone 311, the keypad 312, and/or thedisplay/touchpad 313. The processor 314 in the wireless device 110 mayreceive power from the power source 317 and/or may be configured todistribute the power to the other components in the wireless device 110.The power source 317 may comprise at least one of one or more dry cellbatteries, solar cells, fuel cells, and the like. The processor 314 maybe connected to the GPS chipset 318. The GPS chipset 318 may beconfigured to provide geographic location information of the wirelessdevice 110.

The processor 314 of the wireless device 110 may further be connected toother peripherals 319, which may comprise one or more software and/orhardware modules that provide additional features and/orfunctionalities. For example, the peripherals 319 may comprise at leastone of an accelerometer, a satellite transceiver, a digital camera, auniversal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, and thelike.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110 via a wireless link 330A and/or a wireless link 330Brespectively. In an example, the communication interface 320A of thebase station 1, 120A, may communicate with the communication interface320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110 and/or thebase station 2 120B and the wireless device 110 may be configured tosend and receive transport blocks via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may employ at least one frequency carrier. Accordingto some of various aspects of embodiments, transceiver(s) may beemployed. A transceiver may be a device that comprises both atransmitter and a receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in thecommunication interface 310, 320A, 320B and the wireless link 330A, 330Bare illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A,FIG. 7B, FIG. 8, and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF,etc.) may comprise one or more communication interfaces, one or moreprocessors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers,switches, antennas, and/or the like) may comprise one or moreprocessors, and memory storing instructions that when executed by theone or more processors causes the node to perform certain processesand/or functions. Example embodiments may enable operation ofsingle-carrier and/or multi-carrier communications. Other exampleembodiments may comprise a non-transitory tangible computer readablemedia comprising instructions executable by one or more processors tocause operation of single-carrier and/or multi-carrier communications.Yet other example embodiments may comprise an article of manufacturethat comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a node to enable operation ofsingle-carrier and/or multi-carrier communications. The node may includeprocessors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and code stored in and/or incommunication with a memory device to implement connections, electronicdevice operations, protocol(s), protocol layers, communication drivers,device drivers, hardware operations, combinations thereof, and/or thelike.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 4A shows an example uplink transmitter forat least one physical channel A baseband signal representing a physicaluplink shared channel may perform one or more functions. The one or morefunctions may comprise at least one of: scrambling; modulation ofscrambled bits to generate complex-valued symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; transform precoding to generate complex-valued symbols;precoding of the complex-valued symbols; mapping of precodedcomplex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 4A. These functions are illustrated as examples andit is anticipated that other mechanisms may be implemented in variousembodiments.

An example structure for modulation and up-conversion to the carrierfrequency of the complex-valued SC-FDMA or CP-OFDM baseband signal foran antenna port and/or the complex-valued Physical Random Access CHannel(PRACH) baseband signal is shown in FIG. 4B. Filtering may be employedprior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. Thebaseband signal representing a downlink physical channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

In an example, a gNB may transmit a first symbol and a second symbol onan antenna port, to a wireless device. The wireless device may infer thechannel (e.g., fading gain, multipath delay, etc.) for conveying thesecond symbol on the antenna port, from the channel for conveying thefirst symbol on the antenna port. In an example, a first antenna portand a second antenna port may be quasi co-located if one or morelarge-scale properties of the channel over which a first symbol on thefirst antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals. FIG. 5B is a diagram of an example downlinkchannel mapping and a downlink physical signals. In an example, aphysical layer may provide one or more information transfer services toa MAC and/or one or more higher layers. For example, the physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and with what characteristics data are transferred over theradio interface.

In an example embodiment, a radio network may comprise one or moredownlink and/or uplink transport channels. For example, a diagram inFIG. 5A shows example uplink transport channels comprising Uplink-SharedCHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram inFIG. 5B shows example downlink transport channels comprisingDownlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, andBroadcast CHannel (BCH) 513. A transport channel may be mapped to one ormore corresponding physical channels. For example, UL-SCH 501 may bemapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may bemapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to PhysicalDownlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to PhysicalBroadcast CHannel (PBCH) 516.

There may be one or more physical channels without a correspondingtransport channel. The one or more physical channels may be employed forUplink Control Information (UCI) 509 and/or Downlink Control Information(DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 maycarry UCI 509 from a UE to a base station. For example, PhysicalDownlink Control CHannel (PDCCH) 515 may carry DCI 517 from a basestation to a UE. NR may support UCI 509 multiplexing in PUSCH 503 whenUCI 509 and PUSCH 503 transmissions may coincide in a slot at least inpart. The UCI 509 may comprise at least one of CSI, Acknowledgement(ACK)/Negative Acknowledgement (NACK), and/or scheduling request. TheDCI 517 on PDCCH 515 may indicate at least one of following: one or moredownlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to abase station. For example, the one or more RSs may be at least one ofDemodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/orSounding RS (SRS) 508. In downlink, a base station may transmit (e.g.,unicast, multicast, and/or broadcast) one or more RSs to a UE. Forexample, the one or more RSs may be at least one of PrimarySynchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521,CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a basestation for channel estimation, for example, for coherent demodulationof one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH504). For example, a UE may transmit a base station at least one uplinkDM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least oneuplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. In an example, a base station mayconfigure a UE with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to transmit at one or more symbols of a PUSCH and/or PUCCH. Abase station may semi-statistically configure a UE with a maximum numberof front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UEmay schedule a single-symbol DM-RS and/or double symbol DM-RS based on amaximum number of front-loaded DM-RS symbols, wherein a base station mayconfigure the UE with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, e.g., at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

In an example, whether uplink PT-RS 507 is present or not may depend ona RRC configuration. For example, a presence of uplink PT-RS may beUE-specifically configured. For example, a presence and/or a pattern ofuplink PT-RS 507 in a scheduled resource may be UE-specificallyconfigured by a combination of RRC signaling and/or association with oneor more parameters employed for other purposes (e.g., Modulation andCoding Scheme (MCS)) which may be indicated by DCI. When configured, adynamic presence of uplink PT-RS 507 may be associated with one or moreDCI parameters comprising at least MCS. A radio network may supportplurality of uplink PT-RS densities defined in time/frequency domain.When present, a frequency domain density may be associated with at leastone configuration of a scheduled bandwidth. A UE may assume a sameprecoding for a DMRS port and a PT-RS port. A number of PT-RS ports maybe fewer than a number of DM-RS ports in a scheduled resource. Forexample, uplink PT-RS 507 may be confined in the scheduledtime/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channelstate estimation to support uplink channel dependent scheduling and/orlink adaptation. For example, SRS 508 transmitted by a UE may allow fora base station to estimate an uplink channel state at one or moredifferent frequencies. A base station scheduler may employ an uplinkchannel state to assign one or more resource blocks of good quality foran uplink PUSCH transmission from a UE. A base station maysemi-statistically configure a UE with one or more SRS resource sets.For an SRS resource set, a base station may configure a UE with one ormore SRS resources. An SRS resource set applicability may be configuredby a higher layer (e.g., RRC) parameter. For example, when a higherlayer parameter indicates beam management, a SRS resource in each of oneor more SRS resource sets may be transmitted at a time instant. A UE maytransmit one or more SRS resources in different SRS resource setssimultaneously. A new radio network may support aperiodic, periodicand/or semi-persistent SRS transmissions. A UE may transmit SRSresources based on one or more trigger types, wherein the one or moretrigger types may comprise higher layer signaling (e.g., RRC) and/or oneor more DCI formats (e.g., at least one DCI format may be employed for aUE to select at least one of one or more configured SRS resource sets.An SRS trigger type 0 may refer to an SRS triggered based on a higherlayer signaling. An SRS trigger type 1 may refer to an SRS triggeredbased on one or more DCI formats. In an example, when PUSCH 503 and SRS508 are transmitted in a same slot, a UE may be configured to transmitSRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS506.

In an example, a base station may semi-statistically configure a UE withone or more SRS configuration parameters indicating at least one offollowing: a SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, afrequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one ormore OFDM symbols (e.g., 4 OFDM symbols numbered in increasing orderfrom 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprisePSS/SSS 521 and PBCH 516. In an example, in the frequency domain, anSS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240contiguous subcarriers with the subcarriers numbered in increasing orderfrom 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 mayoccupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may spanacross 3 OFDM symbols and 240 subcarriers. A UE may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, e.g., with respect to Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters. A UE may not assumequasi co-location for other SS/PBCH block transmissions. A periodicityof an SS/PBCH block may be configured by a radio network (e.g., by anRRC signaling) and one or more time locations where the SS/PBCH blockmay be sent may be determined by sub-carrier spacing. In an example, aUE may assume a band-specific sub-carrier spacing for an SS/PBCH blockunless a radio network has configured a UE to assume a differentsub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522.For example, a base station may semi-statistically configure and/orreconfigure a UE with periodic transmission of downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated ad/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation ofCSI-RS resource may be triggered dynamically. In an example, CSI-RSconfiguration may comprise one or more parameters indicating at least anumber of antenna ports. For example, a base station may configure a UEwith 32 ports. A base station may semi-statistically configure a UE withone or more CSI-RS resource sets. One or more CSI-RS resources may beallocated from one or more CSI-RS resource sets to one or more UEs. Forexample, a base station may semi-statistically configure one or moreparameters indicating CSI RS resource mapping, for example, time-domainlocation of one or more CSI-RS resources, a bandwidth of a CSI-RSresource, and/or a periodicity. In an example, a UE may be configured toemploy a same OFDM symbols for downlink CSI-RS 522 and control resourceset (coreset) when the downlink CSI-RS 522 and coreset are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are the outside of PRBs configured for coreset. In anexample, a UE may be configured to employ a same OFDM symbols fordownlink CSI-RS 522 and SSB/PBCH when the downlink CSI-RS 522 andSSB/PBCH are spatially quasi co-located and resource elements associatedwith the downlink CSI-RS 522 are the outside of PRBs configured forSSB/PBCH.

In an example, a UE may transmit one or more downlink DM-RSs 523 to abase station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variableand/or configurable DM-RS patterns for data demodulation. At least onedownlink DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-statisticallyconfigure a UE with a maximum number of front-loaded DM-RS symbols forPDSCH 514. For example, a DM-RS configuration may support one or moreDM-RS ports. For example, for single user-MIMO, a DM-RS configurationmay support at least 8 orthogonal downlink DM-RS ports. For example, formultiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlinkDM-RS ports. A radio network may support, e.g., at least for CP-OFDM, acommon DM-RS structure for DL and UL, wherein a DM-RS location, DM-RSpattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may dependon a RRC configuration. For example, a presence of downlink PT-RS 524may be UE-specifically configured. For example, a presence and/or apattern of downlink PT-RS 524 in a scheduled resource may beUE-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters employed for other purposes(e.g., MCS) which may be indicated by DCI. When configured, a dynamicpresence of downlink PT-RS 524 may be associated with one or more DCIparameters comprising at least MCS. A radio network may supportplurality of PT-RS densities defined in time/frequency domain. Whenpresent, a frequency domain density may be associated with at least oneconfiguration of a scheduled bandwidth. A UE may assume a same precodingfor a DMRS port and a PT-RS port. A number of PT-RS ports may be fewerthan a number of DM-RS ports in a scheduled resource. For example,downlink PT-RS 524 may be confined in the scheduled time/frequencyduration for a UE.

FIG. 6 is a diagram depicting an example frame structure for a carrieras per an aspect of an embodiment of the present disclosure. Amulticarrier OFDM communication system may include one or more carriers,for example, ranging from 1 to 32 carriers, in case of carrieraggregation, or ranging from 1 to 64 carriers, in case of dualconnectivity. Different radio frame structures may be supported (e.g.,for FDD and for TDD duplex mechanisms). FIG. 6 shows an example framestructure. Downlink and uplink transmissions may be organized into radioframes 601. In this example, radio frame duration is 10 ms. In thisexample, a 10 ms radio frame 601 may be divided into ten equally sizedsubframes 602 with 1 ms duration. Subframe(s) may comprise one or moreslots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 604.The number of OFDM symbols 604 in a slot 605 may depend on the cyclicprefix length. For example, a slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may contain downlink, uplink, or a downlink part and an uplinkpart and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as peran aspect of an embodiment of the present disclosure. In the example, agNB may communicate with a wireless device with a carrier with anexample channel bandwidth 700. Arrow(s) in the diagram may depict asubcarrier in a multicarrier OFDM system. The OFDM system may usetechnology such as OFDM technology, SC-FDMA technology, and/or the like.In an example, an arrow 701 shows a subcarrier transmitting informationsymbols. In an example, a subcarrier spacing 702, between two contiguoussubcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120KHz, 240 KHz etc. In an example, different subcarrier spacing maycorrespond to different transmission numerologies. In an example, atransmission numerology may comprise at least: a numerology index; avalue of subcarrier spacing; a type of cyclic prefix (CP). In anexample, a gNB may transmit to/receive from a UE on a number ofsubcarriers 703 in a carrier. In an example, a bandwidth occupied by anumber of subcarriers 703 (transmission bandwidth) may be smaller thanthe channel bandwidth 700 of a carrier, due to guard band 704 and 705.In an example, a guard band 704 and 705 may be used to reduceinterference to and from one or more neighbor carriers. A number ofsubcarriers (transmission bandwidth) in a carrier may depend on thechannel bandwidth of the carrier and the subcarrier spacing. Forexample, a transmission bandwidth, for a carrier with 20 MHz channelbandwidth and 15 KHz subcarrier spacing, may be in number of 1024subcarriers.

In an example, a gNB and a wireless device may communicate with multipleCCs when configured with CA. In an example, different component carriersmay have different bandwidth and/or subcarrier spacing, if CA issupported. In an example, a gNB may transmit a first type of service toa UE on a first component carrier. The gNB may transmit a second type ofservice to the UE on a second component carrier. Different type ofservices may have different service requirement (e.g., data rate,latency, reliability), which may be suitable for transmission viadifferent component carrier having different subcarrier spacing and/orbandwidth. FIG. 7B shows an example embodiment. A first componentcarrier may comprise a first number of subcarriers 706 with a firstsubcarrier spacing 709. A second component carrier may comprise a secondnumber of subcarriers 707 with a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 with athird subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. In an example, a carrier mayhave a transmission bandwidth 801. In an example, a resource grid may bein a structure of frequency domain 802 and time domain 803. In anexample, a resource grid may comprise a first number of OFDM symbols ina subframe and a second number of resource blocks, starting from acommon resource block indicated by higher-layer signaling (e.g. RRCsignaling), for a transmission numerology and a carrier. In an example,in a resource grid, a resource unit identified by a subcarrier index anda symbol index may be a resource element 805. In an example, a subframemay comprise a first number of OFDM symbols 807 depending on anumerology associated with a carrier. For example, when a subcarrierspacing of a numerology of a carrier is 15 KHz, a subframe may have 14OFDM symbols for a carrier. When a subcarrier spacing of a numerology is30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacingof a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. Inan example, a second number of resource blocks comprised in a resourcegrid of a carrier may depend on a bandwidth and a numerology of thecarrier.

As shown in FIG. 8, a resource block 806 may comprise 12 subcarriers. Inan example, multiple resource blocks may be grouped into a ResourceBlock Group (RBG) 804. In an example, a size of a RBG may depend on atleast one of: a RRC message indicating a RBG size configuration; a sizeof a carrier bandwidth; or a size of a bandwidth part of a carrier. Inan example, a carrier may comprise multiple bandwidth parts. A firstbandwidth part of a carrier may have different frequency location and/orbandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control informationcomprising a downlink or uplink resource block assignment to a wirelessdevice. A base station may transmit to or receive from, a wirelessdevice, data packets (e.g. transport blocks) scheduled and transmittedvia one or more resource blocks and one or more slots according toparameters in a downlink control information and/or RRC message(s). Inan example, a starting symbol relative to a first slot of the one ormore slots may be indicated to the wireless device. In an example, a gNBmay transmit to or receive from, a wireless device, data packetsscheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control informationcomprising a downlink assignment to a wireless device via one or morePDCCHs. The downlink assignment may comprise parameters indicating atleast modulation and coding format; resource allocation; and/or HARQinformation related to DL-SCH. In an example, a resource allocation maycomprise parameters of resource block allocation; and/or slotallocation. In an example, a gNB may dynamically allocate resources to awireless device via a Cell-Radio Network Temporary Identifier (C-RNTI)on one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible allocation when its downlink receptionis enabled. The wireless device may receive one or more downlink datapackage on one or more PDSCH scheduled by the one or more PDCCHs, whensuccessfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resourcesfor down link transmission to a wireless device. The gNB may transmitone or more RRC messages indicating a periodicity of the CS grant. ThegNB may transmit a DCI via a PDCCH addressed to a ConfiguredScheduling-RNTI (CS-RNTI) activating the CS resources. The DCI maycomprise parameters indicating that the downlink grant is a CS grant.The CS grant may be implicitly reused according to the periodicitydefined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control informationcomprising an uplink grant to a wireless device via one or more PDCCHs.The uplink grant may comprise parameters indicating at least modulationand coding format; resource allocation; and/or HARQ information relatedto UL-SCH. In an example, a resource allocation may comprise parametersof resource block allocation; and/or slot allocation. In an example, agNB may dynamically allocate resources to a wireless device via a C-RNTIon one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible resource allocation. The wirelessdevice may transmit one or more uplink data package via one or morePUSCH scheduled by the one or more PDCCHs, when successfully detectingthe one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink datatransmission to a wireless device. The gNB may transmit one or more RRCmessages indicating a periodicity of the CS grant. The gNB may transmita DCI via a PDCCH addressed to a CS-RNTI activating the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling viaPDCCH. The DCI may take a format in a plurality of formats. A DCI maycomprise downlink and/or uplink scheduling information (e.g., resourceallocation information, HARQ related parameters, MCS), request for CSI(e.g., aperiodic CQI reports), request for SRS, uplink power controlcommands for one or more cells, one or more timing information (e.g., TBtransmission/reception timing, HARQ feedback timing, etc.), etc. In anexample, a DCI may indicate an uplink grant comprising transmissionparameters for one or more transport blocks. In an example, a DCI mayindicate downlink assignment indicating parameters for receiving one ormore transport blocks. In an example, a DCI may be used by base stationto initiate a contention-free random access at the wireless device. Inan example, the base station may transmit a DCI comprising slot formatindicator (SFI) notifying a slot format. In an example, the base stationmay transmit a DCI comprising pre-emption indication notifying thePRB(s) and/or OFDM symbol(s) where a UE may assume no transmission isintended for the UE. In an example, the base station may transmit a DCIfor group power control of PUCCH or PUSCH or SRS. In an example, a DCImay correspond to an RNTI. In an example, the wireless device may obtainan RNTI in response to completing the initial access (e.g., C-RNTI). Inan example, the base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI(e.g., the wireless device may compute RA-RNTI based on resources usedfor transmission of a preamble). In an example, an RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). In an example, awireless device may monitor a group common search space which may beused by base station for transmitting DCIs that are intended for a groupof UEs. In an example, a group common DCI may correspond to an RNTIwhich is commonly configured for a group of UEs. In an example, awireless device may monitor a UE-specific search space. In an example, aUE specific DCI may correspond to an RNTI configured for the wirelessdevice.

A NR system may support a single beam operation and/or a multi-beamoperation. In a multi-beam operation, a base station may perform adownlink beam sweeping to provide coverage for common control channelsand/or downlink SS blocks, which may comprise at least a PSS, a SSS,and/or PBCH. A wireless device may measure quality of a beam pair linkusing one or more RSs. One or more SS blocks, or one or more CSI-RSresources, associated with a CSI-RS resource index (CRI), or one or moreDM-RSs of PBCH, may be used as RS for measuring quality of a beam pairlink. Quality of a beam pair link may be defined as a reference signalreceived power (RSRP) value, or a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. A RS resource and DM-RSs of a control channel may be calledQCLed when a channel characteristics from a transmission on an RS to awireless device, and that from a transmission on a control channel to awireless device, are similar or same under a configured criterion. In amulti-beam operation, a wireless device may perform an uplink beamsweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH onone or more beam pair links simultaneously depending on a capability ofa wireless device. This may increase robustness against beam pair linkblocking. A base station may transmit one or more messages to configurea wireless device to monitor PDCCH on one or more beam pair links indifferent PDCCH OFDM symbols. For example, a base station may transmithigher layer signaling (e.g. RRC signaling) or MAC CE comprisingparameters related to the Rx beam setting of a wireless device formonitoring PDCCH on one or more beam pair links. A base station maytransmit indication of spatial QCL assumption between an DL RS antennaport(s) (for example, cell-specific CSI-RS, or wireless device-specificCSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RSantenna port(s) for demodulation of DL control channel Signaling forbeam indication for a PDCCH may be MAC CE signaling, or RRC signaling,or DCI signaling, or specification-transparent and/or implicit method,and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. The base station may transmit DCI (e.g.downlink grants) comprising information indicating the RS antennaport(s). The information may indicate RS antenna port(s) which may beQCL-ed with the DM-RS antenna port(s). Different set of DM-RS antennaport(s) for a DL data channel may be indicated as QCL with different setof the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. For example, in a multi-beamoperation, a base station 120 may transmit SS blocks in multiple beams,together forming a SS burst 940. One or more SS blocks may betransmitted on one beam. If multiple SS bursts 940 are transmitted withmultiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation forestimating a beam quality of a links between a wireless device and abase station. A beam may be associated with a CSI-RS. For example, awireless device may, based on a RSRP measurement on CSI-RS, report abeam index, as indicated in a CRI for downlink beam selection, andassociated with a RSRP value of a beam. A CSI-RS may be transmitted on aCSI-RS resource including at least one of one or more antenna ports, oneor more time or frequency radio resources. A CSI-RS resource may beconfigured in a cell-specific way by common RRC signaling, or in awireless device-specific way by dedicated RRC signaling, and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be transmitted periodically, or using aperiodictransmission, or using a multi-shot or semi-persistent transmission. Forexample, in a periodic transmission in FIG. 9A, a base station 120 maytransmit configured CSI-RS resources 940 periodically using a configuredperiodicity in a time domain. In an aperiodic transmission, a configuredCSI-RS resource may be transmitted in a dedicated time slot. In amulti-shot or semi-persistent transmission, a configured CSI-RS resourcemay be transmitted within a configured period. Beams used for CSI-RStransmission may have different beam width than beams used for SS-blockstransmission.

FIG. 9B is an example of a beam management procedure in an example newradio network. A base station 120 and/or a wireless device 110 mayperform a downlink L1/L2 beam management procedure. One or more of thefollowing downlink L1/L2 beam management procedures may be performedwithin one or more wireless devices 110 and one or more base stations120. In an example, a P-1 procedure 910 may be used to enable thewireless device 110 to measure one or more Transmission (Tx) beamsassociated with the base station 120 to support a selection of a firstset of Tx beams associated with the base station 120 and a first set ofRx beam(s) associated with a wireless device 110. For beamforming at abase station 120, a base station 120 may sweep a set of different TXbeams. For beamforming at a wireless device 110, a wireless device 110may sweep a set of different Rx beams. In an example, a P-2 procedure920 may be used to enable a wireless device 110 to measure one or moreTx beams associated with a base station 120 to possibly change a firstset of Tx beams associated with a base station 120. A P-2 procedure 920may be performed on a possibly smaller set of beams for beam refinementthan in the P-1 procedure 910. A P-2 procedure 920 may be a special caseof a P-1 procedure 910. In an example, a P-3 procedure 930 may be usedto enable a wireless device 110 to measure at least one Tx beamassociated with a base station 120 to change a first set of Rx beamsassociated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reportsto a base station 120. In one or more beam management reports, awireless device 110 may indicate some beam pair quality parameters,comprising at least, one or more beam identifications; RSRP; PrecodingMatrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator(RI) of a subset of configured beams. Based on one or more beammanagement reports, a base station 120 may transmit to a wireless device110 a signal indicating that one or more beam pair links are one or moreserving beams. A base station 120 may transmit PDCCH and PDSCH for awireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a BandwidthAdaptation (BA). In an example, receive and/or transmit bandwidthsconfigured by an UE employing a BA may not be large. For example, areceive and/or transmit bandwidths may not be as large as a bandwidth ofa cell. Receive and/or transmit bandwidths may be adjustable. Forexample, a UE may change receive and/or transmit bandwidths, e.g., toshrink during period of low activity to save power. For example, a UEmay change a location of receive and/or transmit bandwidths in afrequency domain, e.g. to increase scheduling flexibility. For example,a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cellmay be referred to as a Bandwidth Part (BWP). A base station mayconfigure a UE with one or more BWPs to achieve a BA. For example, abase station may indicate, to a UE, which of the one or more(configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050)with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g. RRC layer)for a cell a set of one or more BWPs (e.g., at most four BWPs) forreceptions by the UE (DL BWP set) in a DL bandwidth by at least oneparameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs)for transmissions by a UE (UL BWP set) in an UL bandwidth by at leastone parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one ormore UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA),a base station may configure a UE at least with one or more DL BWPs(e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least oneof a location and number of contiguous PRBs, a subcarrier spacing, or acyclic prefix, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a UE is configured with a secondary carrier on a primary cell, the UEmay be configured with an initial BWP for random access procedure on asecondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that acenter frequency for a DL BWP may be same as a center frequency for a ULBWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPsor one or more UL BWPs, respectively, a base statin maysemi-statistically configure a UE for a cell with one or more parametersindicating at least one of following: a subcarrier spacing; a cyclicprefix; a number of contiguous PRBs; an index in the set of one or moreDL BWPs and/or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; a DCI detection to aPDSCH reception timing; a PDSCH reception to a HARQ-ACK transmissiontiming value; a DCI detection to a PUSCH transmission timing value; anoffset of a first PRB of a DL bandwidth or an UL bandwidth,respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell,a base station may configure a UE with one or more control resource setsfor at least one type of common search space and/or one UE-specificsearch space. For example, a base station may not configure a UE withouta common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station mayconfigure a UE with one or more resource sets for one or more PUCCHtransmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicatorfield value may indicate an active DL BWP, from a configured DL BWP set,for one or more DL receptions. If a DCI comprises a BWP indicator field,a BWP indicator field value may indicate an active UL BWP, from aconfigured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statisticallyconfigure a UE with a default DL BWP among configured DL BWPs. If a UEis not provided a default DL BWP, a default BWP may be an initial activeDL BWP.

In an example, a base station may configure a UE with a timer value fora PCell. For example, a UE may start a timer, referred to as BWPinactivity timer, when a UE detects a DCI indicating an active DL BWP,other than a default DL BWP, for a paired spectrum operation or when aUE detects a DCI indicating an active DL BWP or UL BWP, other than adefault DL BWP or UL BWP, for an unpaired spectrum operation. The UE mayincrement the timer by an interval of a first value (e.g., the firstvalue may be 1 millisecond or 0.5 milliseconds) if the UE does notdetect a DCI during the interval for a paired spectrum operation or foran unpaired spectrum operation. In an example, the timer may expire whenthe timer is equal to the timer value. A UE may switch to the default DLBWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of BWP inactivity timer(for example, the second BWP may be a default BWP). For example, FIG. 10is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2(1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a defaultBWP. BWP1 (1010) may be an initial active BWP. In an example, a UE mayswitch an active BWP from BWP1 1010 to BWP2 1020 in response to anexpiry of BWP inactivity timer. For example, a UE may switch an activeBWP from BWP2 1020 to BWP3 1030 in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in responseto receiving a DCI indicating an active BWP and/or in response to anexpiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a defaultDL BWP among configured DL BWPs and a timer value, UE procedures on asecondary cell may be same as on a primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DLBWP and a first active UL BWP on a secondary cell or carrier, a UE mayemploy an indicated DL BWP and an indicated UL BWP on a secondary cellas a respective first active DL BWP and first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity(e.g. dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A is an example diagram of a protocol structure of awireless device 110 (e.g. UE) with CA and/or multi connectivity as peran aspect of an embodiment. FIG. 11B is an example diagram of a protocolstructure of multiple base stations with CA and/or multi connectivity asper an aspect of an embodiment. The multiple base stations may comprisea master node, MN 1130 (e.g. a master node, a master base station, amaster gNB, a master eNB, and/or the like) and a secondary node, SN 1150(e.g. a secondary node, a secondary base station, a secondary gNB, asecondary eNB, and/or the like). A master node 1130 and a secondary node1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception/transmissionfunctions in an RRC connected state, may be configured to utilize radioresources provided by multiple schedulers of a multiple base stations.Multiple base stations may be inter-connected via a non-ideal or idealbackhaul (e.g. Xn interface, X2 interface, and/or the like). A basestation involved in multi connectivity for a certain wireless device mayperform at least one of two different roles: a base station may eitheract as a master base station or as a secondary base station. In multiconnectivity, a wireless device may be connected to one master basestation and one or more secondary base stations. In an example, a masterbase station (e.g. the MN 1130) may provide a master cell group (MCG)comprising a primary cell and/or one or more secondary cells for awireless device (e.g. the wireless device 110). A secondary base station(e.g. the SN 1150) may provide a secondary cell group (SCG) comprising aprimary secondary cell (PSCell) and/or one or more secondary cells for awireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a beareremploys may depend on how a bearer is setup. In an example, threedifferent type of bearer setup options may be supported: an MCG bearer,an SCG bearer, and/or a split bearer. A wireless device mayreceive/transmit packets of an MCG bearer via one or more cells of theMCG, and/or may receive/transmits packets of an SCG bearer via one ormore cells of an SCG. Multi-connectivity may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not beconfigured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmitand/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer viaan SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one ofa master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and oneof a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119);and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), aPDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and aMAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondarybase station (e.g. SN 1150) may transmit/receive: packets of an MCGbearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and amaster node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via amaster or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), asecondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and asecondary node MAC layer (e.g. SN MAC 1148); packets of a split bearervia a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), amaster or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SNRLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g.MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities: one MAC entity (e.g. MN MAC 1118) for a master base station,and other MAC entities (e.g. SN MAC 1119) for a secondary base station.In multi-connectivity, a configured set of serving cells for a wirelessdevice may comprise two subsets: an MCG comprising serving cells of amaster base station, and SCGs comprising serving cells of a secondarybase station. For an SCG, one or more of following configurations may beapplied: at least one cell of an SCG has a configured UL CC and at leastone cell of a SCG, named as primary secondary cell (PSCell, PCell ofSCG, or sometimes called PCell), is configured with PUCCH resources;when an SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or a number of NR RLC retransmissions hasbeen reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, forsplit bearer, a DL data transfer over a master base station may bemaintained; an NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer; PCell and/or PSCell may not be de-activated; PSCellmay be changed with a SCG change procedure (e.g. with security keychange and a RACH procedure); and/or a bearer type change between asplit bearer and a SCG bearer or simultaneous configuration of a SCG anda split bearer may or may not supported.

With respect to interaction between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be applied: a master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice; a master base station may (e.g. based on received measurementreports, traffic conditions, and/or bearer types) may decide to requesta secondary base station to provide additional resources (e.g. servingcells) for a wireless device; upon receiving a request from a masterbase station, a secondary base station may create/modify a containerthat may result in configuration of additional serving cells for awireless device (or decide that the secondary base station has noresource available to do so); for a UE capability coordination, a masterbase station may provide (a part of) an AS configuration and UEcapabilities to a secondary base station; a master base station and asecondary base station may exchange information about a UE configurationby employing of RRC containers (inter-node messages) carried via Xnmessages; a secondary base station may initiate a reconfiguration of thesecondary base station existing serving cells (e.g. PUCCH towards thesecondary base station); a secondary base station may decide which cellis a PSCell within a SCG; a master base station may or may not changecontent of RRC configurations provided by a secondary base station; incase of a SCG addition and/or a SCG SCell addition, a master basestation may provide recent (or the latest) measurement results for SCGcell(s); a master base station and secondary base stations may receiveinformation of SFN and/or subframe offset of each other from OAM and/orvia an Xn interface, (e.g. for a purpose of DRX alignment and/oridentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signaling may be used for sending requiredsystem information of a cell as for CA, except for a SFN acquired from aMIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival during RRC_CONNECTED when UL synchronization status isnon-synchronized, transition from RRC_Inactive, and/or request for othersystem information. For example, a PDCCH order, a MAC entity, and/or abeam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least oneof a contention based random access procedure and a contention freerandom access procedure. For example, a contention based random accessprocedure may comprise, one or more Msg 1 1220 transmissions, one ormore Msg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. For example, a contention free random accessprocedure may comprise one or more Msg 1 1220 transmissions and one ormore Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, orbroadcast), to a UE, a RACH configuration 1210 via one or more beams.The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: available set of PRACH resourcesfor a transmission of a random access preamble, initial preamble power(e.g., random access preamble initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., random access preamble powerramping step), random access preamble index, a maximum number ofpreamble transmission, preamble group A and group B, a threshold (e.g.,message size) to determine the groups of random access preambles, a setof one or more random access preambles for system information requestand corresponding PRACH resource(s), if any, a set of one or more randomaccess preambles for beam failure recovery request and correspondingPRACH resource(s), if any, a time window to monitor RA response(s), atime window to monitor response(s) on beam failure recovery request,and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of arandom access preamble. For a contention based random access procedure,a UE may select a SS block with a RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a UE may select one or morerandom access preambles from a group A or a group B depending on apotential Msg3 1240 size. If a random access preambles group B does notexist, a UE may select the one or more random access preambles from agroup A. A UE may select a random access preamble index randomly (e.g.with equal probability or a normal distribution) from one or more randomaccess preambles associated with a selected group. If a base stationsemi-statistically configures a UE with an association between randomaccess preambles and SS blocks, the UE may select a random accesspreamble index randomly with equal probability from one or more randomaccess preambles associated with a selected SS block and a selectedgroup.

For example, a UE may initiate a contention free random access procedurebased on a beam failure indication from a lower layer. For example, abase station may semi-statistically configure a UE with one or morecontention free PRACH resources for beam failure recovery requestassociated with at least one of SS blocks and/or CSI-RSs. If at leastone of SS blocks with a RSRP above a first RSRP threshold amongstassociated SS blocks or at least one of CSI-RSs with a RSRP above asecond RSRP threshold amongst associated CSI-RSs is available, a UE mayselect a random access preamble index corresponding to a selected SSblock or CSI-RS from a set of one or more random access preambles forbeam failure recovery request.

For example, a UE may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. If a base station does not configure a UE with at least onecontention free PRACH resource associated with SS blocks or CSI-RS, theUE may select a random access preamble index. If a base stationconfigures a UE with one or more contention free PRACH resourcesassociated with SS blocks and at least one SS block with a RSRP above afirst RSRP threshold amongst associated SS blocks is available, the UEmay select the at least one SS block and select a random access preamblecorresponding to the at least one SS block. If a base station configuresa UE with one or more contention free PRACH resources associated withCSI-RSs and at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available, the UE may selectthe at least one CSI-RS and select a random access preamblecorresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting theselected random access preamble. For example, if a UE selects an SSblock and is configured with an association between one or more PRACHoccasions and one or more SS blocks, the UE may determine an PRACHoccasion from one or more PRACH occasions corresponding to a selected SSblock. For example, if a UE selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs,the UE may determine a PRACH occasion from one or more PRACH occasionscorresponding to a selected CSI-RS. A UE may transmit, to a basestation, a selected random access preamble via a selected PRACHoccasions. A UE may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. A UE may determine a RA-RNTIassociated with a selected PRACH occasions in which a selected randomaccess preamble is transmitted. For example, a UE may not determine aRA-RNTI for a beam failure recovery request. A UE may determine anRA-RNTI at least based on an index of a first OFDM symbol and an indexof a first slot of a selected PRACH occasions, and/or an uplink carrierindex for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random accessresponse, Msg 2 1230. A UE may start a time window (e.g., ra-ResponseWindow) to monitor a random access response. For beam failure recoveryrequest, a base station may configure a UE with a different time window(e.g., bfr-ResponseWindow) to monitor response on beam failure recoveryrequest. For example, a UE may start a time window (e.g.,ra-ResponseWindow or bfr-ResponseWindow) at a start of a first PDCCHoccasion after a fixed duration of one or more symbols from an end of apreamble transmission. If a UE transmits multiple preambles, the UE maystart a time window at a start of a first PDCCH occasion after a fixedduration of one or more symbols from an end of a first preambletransmission. A UE may monitor a PDCCH of a cell for at least one randomaccess response identified by a RA-RNTI or for at least one response tobeam failure recovery request identified by a C-RNTI while a timer for atime window is running.

In an example, a UE may consider a reception of random access responsesuccessful if at least one random access response comprises a randomaccess preamble identifier corresponding to a random access preambletransmitted by the UE. A UE may consider the contention free randomaccess procedure successfully completed if a reception of random accessresponse is successful. If a contention free random access procedure istriggered for a beam failure recovery request, a UE may consider acontention free random access procedure successfully complete if a PDCCHtransmission is addressed to a C-RNTI. In an example, if at least onerandom access response comprises a random access preamble identifier, aUE may consider the random access procedure successfully completed andmay indicate a reception of an acknowledgement for a system informationrequest to upper layers. If a UE has signaled multiple preambletransmissions, the UE may stop transmitting remaining preambles (if any)in response to a successful reception of a corresponding random accessresponse.

In an example, a UE may perform one or more Msg 3 1240 transmissions inresponse to a successful reception of random access response (e.g., fora contention based random access procedure). A UE may adjust an uplinktransmission timing based on a timing advanced command indicated by arandom access response and may transmit one or more transport blocksbased on an uplink grant indicated by a random access response.Subcarrier spacing for PUSCH transmission for Msg3 1240 may be providedby at least one higher layer (e.g. RRC) parameter. A UE may transmit arandom access preamble via PRACH and Msg3 1240 via PUSCH on a same cell.A base station may indicate an UL BWP for a PUSCH transmission of Msg31240 via system information block. A UE may employ HARQ for aretransmission of Msg 3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting asame preamble to a base station and receive, from the base station, asame random access response comprising an identity (e.g., TC-RNTI).Contention resolution 1250 may ensure that a UE does not incorrectly usean identity of another UE. For example, contention resolution 1250 maybe based on C-RNTI on PDCCH or a UE contention resolution identity onDL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UEmay perform contention resolution 1250 based on a reception of a PDCCHtransmission that is addressed to the C-RNTI. In response to detectionof a C-RNTI on a PDCCH, a UE may consider contention resolution 1250successful and may consider a random access procedure successfullycompleted. If a UE has no valid C-RNTI, a contention resolution may beaddressed by employing a TC-RNTI. For example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises a UE contention resolutionidentity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UEmay consider the contention resolution 1250 successful and may considerthe random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of anembodiment. In an example, a wireless device may be configured tooperate in a multi-connectivity mode. A wireless device in RRC_CONNECTEDwith multiple RX/TX may be configured to utilize radio resourcesprovided by multiple schedulers located in a plurality of base stations.The plurality of base stations may be connected via a non-ideal or idealbackhaul over the Xn interface. In an example, a base station in aplurality of base stations may act as a master base station or as asecondary base station. A wireless device may be connected to one masterbase station and one or more secondary base stations. A wireless devicemay be configured with multiple MAC entities, e.g. one MAC entity formaster base station, and one or more other MAC entities for secondarybase station(s). In an example, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 illustrates an examplestructure for MAC entities when MCG and SCG are configured for awireless device.

In an example, at least one cell in a SCG may have a configured UL CC,wherein a cell of at least one cell may be called PSCell or PCell ofSCG, or sometimes may be simply called PCell. A PSCell may be configuredwith PUCCH resources. In an example, when a SCG is configured, there maybe at least one SCG bearer or one split bearer. In an example, upondetection of a physical layer problem or a random access problem on aPSCell, or upon reaching a number of RLC retransmissions associated withthe SCG, or upon detection of an access problem on a PSCell during a SCGaddition or a SCG change: an RRC connection re-establishment proceduremay not be triggered, UL transmissions towards cells of an SCG may bestopped, a master base station may be informed by a UE of a SCG failuretype and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transferand radio resource allocation to upper layers (e.g. 1310 or 1320). A MACsublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360).A MAC sublayer may provide data transfer services on logical channels.To accommodate different kinds of data transfer services, multiple typesof logical channels may be defined. A logical channel may supporttransfer of a particular type of information. A logical channel type maybe defined by what type of information (e.g., control or data) istransferred. For example, BCCH, PCCH, CCCH and DCCH may be controlchannels and DTCH may be a traffic channel. In an example, a first MACentity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCHand MAC control elements. In an example, a second MAC entity (e.g. 1320)may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,signaling of scheduling request or measurements (e.g. CQI). In anexample, in dual connectivity, two MAC entities may be configured for awireless device: one for MCG and one for SCG. A MAC entity of wirelessdevice may handle a plurality of transport channels. In an example, afirst MAC entity may handle first transport channels comprising a PCCHof MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one ormore first UL-SCHs of MCG and one or more first RACHs of MCG. In anexample, a second MAC entity may handle second transport channelscomprising a second BCH of SCG, one or more second DL-SCHs of SCG, oneor more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells,there may be multiple DL-SCHs and there may be multiple UL-SCHs as wellas multiple RACHs per MAC entity. In an example, there may be one DL-SCHand UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero orone UL-SCH and zero or one RACH for an SCell. A DL-SCH may supportreceptions using different numerologies and/or TTI duration within a MACentity. A UL-SCH may also support transmissions using differentnumerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and maycontrol these functions with a control (e.g. 1355 or 1365) element.Functions performed by a MAC entity may comprise mapping between logicalchannels and transport channels (e.g., in uplink or downlink),multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TB) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g. 1352 or 1362) of MAC SDUs to one or different logical channelsfrom transport blocks (TB) delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink or downlink(e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or1361). A MAC entity may handle a random access process (e.g. 1354 or1364).

FIG. 14 is an example diagram of a RAN architecture comprising one ormore base stations. In an example, a protocol stack (e.g. RRC, SDAP,PDCP, RLC, MAC, and PHY) may be supported at a node. A base station(e.g. 120A or 120B) may comprise a base station central unit (CU) (e.g.gNB-CU 1420A or 1420B) and at least one base station distributed unit(DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functional splitis configured. Upper protocol layers of a base station may be located ina base station CU, and lower layers of the base station may be locatedin the base station DUs. An F1 interface (e.g. CU-DU interface)connecting a base station CU and base station DUs may be an ideal ornon-ideal backhaul. F1-C may provide a control plane connection over anF1 interface, and F1-U may provide a user plane connection over the F1interface. In an example, an Xn interface may be configured between basestation CUs.

In an example, a base station CU may comprise an RRC function, an SDAPlayer, and a PDCP layer, and base station DUs may comprise an RLC layer,a MAC layer, and a PHY layer. In an example, various functional splitoptions between a base station CU and base station DUs may be possibleby locating different combinations of upper protocol layers (RANfunctions) in a base station CU and different combinations of lowerprotocol layers (RAN functions) in base station DUs. A functional splitmay support flexibility to move protocol layers between a base stationCU and base station DUs depending on service requirements and/or networkenvironments.

In an example, functional split options may be configured per basestation, per base station CU, per base station DU, per UE, per bearer,per slice, or with other granularities. In per base station CU split, abase station CU may have a fixed split option, and base station DUs maybe configured to match a split option of a base station CU. In per basestation DU split, a base station DU may be configured with a differentsplit option, and a base station CU may provide different split optionsfor different base station DUs. In per UE split, a base station (basestation CU and at least one base station DUs) may provide differentsplit options for different wireless devices. In per bearer split,different split options may be utilized for different bearers. In perslice splice, different split options may be applied for differentslices.

FIG. 15 is an example diagram showing RRC state transitions of awireless device. In an example, a wireless device may be in at least oneRRC state among an RRC connected state (e.g. RRC Connected 1530,RRC_Connected), an RRC idle state (e.g. RRC Idle 1510, RRC_Idle), and/oran RRC inactive state (e.g. RRC Inactive 1520, RRC_Inactive). In anexample, in an RRC connected state, a wireless device may have at leastone RRC connection with at least one base station (e.g. gNB and/or eNB),which may have a UE context of the wireless device. A UE context (e.g. awireless device context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an example, in an RRC idle state, a wireless device may nothave an RRC connection with a base station, and a UE context of awireless device may not be stored in a base station. In an example, inan RRC inactive state, a wireless device may not have an RRC connectionwith a base station. A UE context of a wireless device may be stored ina base station, which may be called as an anchor base station (e.g. lastserving base station).

In an example, a wireless device may transition a UE RRC state betweenan RRC idle state and an RRC connected state in both ways (e.g.connection release 1540 or connection establishment 1550; or connectionreestablishment) and/or between an RRC inactive state and an RRCconnected state in both ways (e.g. connection inactivation 1570 orconnection resume 1580). In an example, a wireless device may transitionits RRC state from an RRC inactive state to an RRC idle state (e.g.connection release 1560).

In an example, an anchor base station may be a base station that maykeep a UE context (a wireless device context) of a wireless device atleast during a time period that a wireless device stays in a RANnotification area (RNA) of an anchor base station, and/or that awireless device stays in an RRC inactive state. In an example, an anchorbase station may be a base station that a wireless device in an RRCinactive state was lastly connected to in a latest RRC connected stateor that a wireless device lastly performed an RNA update procedure in.In an example, an RNA may comprise one or more cells operated by one ormore base stations. In an example, a base station may belong to one ormore RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from anRRC connected state to an RRC inactive state in a base station. Awireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RANpaging message) to base stations of an RNA to reach to a wireless devicein an RRC inactive state, and/or the base stations receiving the messagefrom the anchor base station may broadcast and/or multicast anothermessage (e.g. paging message) to wireless devices in their coveragearea, cell coverage area, and/or beam coverage area associated with theRNA through an air interface.

In an example, when a wireless device in an RRC inactive state movesinto a new RNA, the wireless device may perform an RNA update (RNAU)procedure, which may comprise a random access procedure by the wirelessdevice and/or a UE context retrieve procedure. A UE context retrieve maycomprise: receiving, by a base station from a wireless device, a randomaccess preamble; and fetching, by a base station, a UE context of thewireless device from an old anchor base station. Fetching may comprise:sending a retrieve UE context request message comprising a resumeidentifier to the old anchor base station and receiving a retrieve UEcontext response message comprising the UE context of the wirelessdevice from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state mayselect a cell to camp on based on at least a on measurement results forone or more cells, a cell where a wireless device may monitor an RNApaging message and/or a core network paging message from a base station.In an example, a wireless device in an RRC inactive state may select acell to perform a random access procedure to resume an RRC connectionand/or to transmit one or more packets to a base station (e.g. to anetwork). In an example, if a cell selected belongs to a different RNAfrom an RNA for a wireless device in an RRC inactive state, the wirelessdevice may initiate a random access procedure to perform an RNA updateprocedure. In an example, if a wireless device in an RRC inactive statehas one or more packets, in a buffer, to transmit to a network, thewireless device may initiate a random access procedure to transmit oneor more packets to a base station of a cell that the wireless deviceselects. A random access procedure may be performed with two messages(e.g. 2 stage random access) and/or four messages (e.g. 4 stage randomaccess) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplinkpackets from a wireless device in an RRC inactive state may fetch a UEcontext of a wireless device by transmitting a retrieve UE contextrequest message for the wireless device to an anchor base station of thewireless device based on at least one of an AS context identifier, anRNA identifier, a base station identifier, a resume identifier, and/or acell identifier received from the wireless device. In response tofetching a UE context, a base station may transmit a path switch requestfor a wireless device to a core network entity (e.g. AMF, MME, and/orthe like). A core network entity may update a downlink tunnel endpointidentifier for one or more bearers established for the wireless devicebetween a user plane core network entity (e.g. UPF, S-GW, and/or thelike) and a RAN node (e.g. the base station), e.g. changing a downlinktunnel endpoint identifier from an address of the anchor base station toan address of the base station.

A gNB may communicate with a wireless device via a wireless networkemploying one or more new radio technologies. The one or more radiotechnologies may comprise at least one of: multiple technologies relatedto physical layer; multiple technologies related to medium accesscontrol layer; and/or multiple technologies related to radio resourcecontrol layer. Example embodiments of enhancing the one or more radiotechnologies may improve performance of a wireless network. Exampleembodiments may increase the system throughput, or data rate oftransmission. Example embodiments may reduce battery consumption of awireless device. Example embodiments may improve latency of datatransmission between a gNB and a wireless device. Example embodimentsmay improve network coverage of a wireless network. Example embodimentsmay improve transmission efficiency of a wireless network.

In an example, a wireless device may receive configuration parameters ofa plurality of configured grant configurations on cell. In an example,the plurality of configured grant configurations may be for a BWP of acell. The wireless device may receive one or more messages comprisingconfiguration parameters of the plurality of configured grantconfigurations. In an example, a configured grant configuration in theplurality of configured grant configurations may be configured with aconfigured grant configuration identifier. In an example, a configuredgrant configuration in the plurality of configured grant configurationsmay be a Type 1 configured grant configuration. In an example, aconfigured grant configuration in the plurality of configured grantconfigurations maybe a Type 2 configured grant configuration.

In an example, a wireless device may support separate activation ofdifferent configured grant Type 2 configurations for a BWP of a servingcell. In an example, for separate activation of the different configuredgrant Type 2 configurations, the wireless device may receive separateactivation DCIs (e.g., one DCI for each configured grant configurationto be activated).

In an example, the wireless device may support joint activation of aplurality of configured grant configurations. With joint activation ofmultiple configured grant configuration, the wireless device may receiveone DCI for activation of two or more configured grant Type 2configurations.

In an example, a wireless device may support separate release ofdifferent configured grant Type 2 configurations for a BWP of a servingcell. In an example, for separate release of the different configuredgrant Type 2 configurations, the wireless device may receive separateDCIs indicating release (e.g., one DCI for each configured grantconfiguration to be release).

In an example, the wireless device may support joint release of aplurality of configured grant configurations. With joint release ofmultiple configured grant configuration, the wireless device may receiveone DCI for release of two or more configured grant Type 2configurations.

In an example, a wireless device may be configured with one or morefirst configured grant configuration of a first Type and one or moresecond configured grant configurations of a second type. The first typeconfigured grant configuration may be a Type 1 configured grantconfiguration. A wireless device may activate a plurality of resourcesin response to receiving configuration parameters of a Type 1 configuredgrant. The second type configured grant configuration may be a Type 2configured grant. A wireless device may activate a plurality ofresources in response to receiving configuration parameters of a Type 2configured grant and receiving an activation DCI indicating activatingthe Type 2 configured grant.

In an example, a wireless device support multiple active configuredgrant configurations with different Types for a given BWP of a servingcell. In an example, the wireless device may indicate (e.g., in acapability message), that the wireless device may support multipleactive configured grant configurations of different types. The wirelessdevice may receive (e.g., in response to indicating the support ofactive configured grant configurations with different Types for a givenBWP of a serving cell), configuration parameters and/or activation DCIsindicating multiple active configured grant with different Types (e.g.,one or more active configured grant Type 1 and one or more activeconfigured grant Type 2) on a BWP of a cell of the wireless device.

In an example, a wireless device may receive configuration parameters ofa plurality of downlink SPS configurations. In an example, the pluralityof downlink SPS configurations may be for a downlink BWP of a cell. Thewireless device may receive one or more messages comprisingconfiguration parameters of the plurality of downlink SPSconfigurations. In an example, a downlink SPS configuration in theplurality of downlink SPS configurations may be configured with adownlink SPS configuration identifier.

In an example, a wireless device may support separate activation fordifferent DL SPS configurations for a given BWP of a serving cell. In anexample, for separate activation of different DL SPS configurations fora given BWP of a serving cell, the wireless device may receive separateactivation DCIs (e.g., one DCI for each downlink SPS configuration to beactivated).

In an example, the wireless device may support joint activation of aplurality of downlink SPS configurations. With joint activation ofmultiple downlink SPS configuration, the wireless device may receive oneDCI for activation of two or more downlink SPS configurations.

In an example, a wireless device may support separate release ofdifferent DL SPS configurations for a given BWP of a serving cell. In anexample, for separate release of different DL SPS configurations for agiven BWP of a serving cell, the wireless device may receive separaterelease DCIs (e.g., one DCI for each downlink SPS configuration to bereleased).

In an example, a wireless device may support joint release of aplurality of downlink SPS configurations. With joint release of multipledownlink SPS configurations, the wireless device may receive one DCI forrelease of two or more downlink SPS configurations.

In an example downlink SPS may be configured for a wireless device tosupport periodic traffic for various URLLC use cases such as powerdistribution, factory automation, and transport industry (includingremote driving. Support of multiple simultaneous active DL SPSconfigurations for a given BWP may reduce the latency and provide thepossibility to support different service types for a wireless device.

In an example, a downlink SPS configuration may indicate a periodicityof downlink SPS assignments. In an example, a periodicity of shorterthan 1 slot may be supported by a wireless device. In an example,support for multiple active downlink SPS configurations on a cell (e.g.,a DL BWP of a cell) and/or shorter periodicities of DL SPS may requireenhancements to HARQ-ACK codebook determination processes. In anexample, a larger PUCCH payload may be needed to carry the HARQ ACK bitscorresponding to several SPS PDSCH in the a slot. In an example, in caseof DL SPS with dynamic scheduling, the size of semi-static HARQ codebookmay need to be increased to support DL SPS with smaller periodicities.In an example, a number of HARQ-ACK bits, bit position, and PUCCHresource determination need to be taken into account. In an example,HARQ-ACK for multiple SPS PDSCHs may need to be aggregated.

In an example, a wireless device may receive configuration parameters ofan uplink configured grant configuration on a bandwidth part of a cell.In an example, the wireless device may activate a plurality of uplinkresources, associated with the uplink configured grant configuration,based on the receiving the configuration parameters and the uplinkconfigured grant configuration being of a first type (e.g., Type 1configured grant). In an example, the wireless device may activate aplurality of uplink resources, associated with the uplink configuredgrant configuration, based on the receiving the configuration parametersand an activation DCI indicating activation of the uplink configuredgrant configuration and the uplink configured grant configuration beingof a second type (e.g., Type 2 configured grant).

In an example, the wireless device may transmit a transport block basedon a first uplink resource, associated with an uplink configured grantconfiguration, in response to having data that can be transmitted viathe first uplink resource. The uplink configured grant configuration maybe associated with a first service type (e.g., URLLC) and the wirelessdevice may transmit at the first resource if data corresponding to thefirst service type being available.

The wireless device may receive a DCI indicating an uplink grant (e.g.,a dynamic grant) for transmission via a second resource that has overlap(e.g., time overlap) and/or conflict/collision with the first resource.A prioritization procedure may be used to determine the priority betweenthe configured grant (for the first uplink resource) and the dynamicgrant (for the second uplink resource).

In an example, the priority may be determined at the MAC layer, e.g.,based on data in a first transport block for transmission via thedynamic grant and data of a second transport block for transmissionbased on the configured grant. The MAC layer may indicate to thePhysical layer to transmit or drop which transport block.

In an example, the priority may be determined at the Physical layerbased on Physical layer channel(s)/signal(s)/parameter(s) to enable theprioritization. In an example, to select between the dynamic grant andthe configured grant, one or more parameters in a DCI indicating thedynamic grant may be used. In an example, a length and/or resourcepriority or a priority indicator in the DCI may indicate the priority.

In an example, Semi-Persistent Scheduling (SPS) may be configured by RRCper Serving Cell and per BWP. In an example, activation and deactivationof the DL SPS may be independent among the Serving Cells. For the DLSPS, a DL assignment may be provided by PDCCH, and stored or clearedbased on L1 signalling indicating SPS activation or deactivation.

In an example, RRC may configure the following parameters when SPS isconfigured: cs-RNTI: CS-RNTI for activation, deactivation, andretransmission; nrofHARQ-Processes: the number of configured HARQprocesses for SPS; periodicity: periodicity of configured downlinkassignment for SPS.

In an example, when SPS is released by upper layers, the correspondingconfigurations may be released.

In an example, in response to a downlink assignment being configured forSPS, the MAC entity may consider sequentially that the Nth downlinkassignment occurs in the slot for which:(numberOfSlotsPerFrame×SFN+slot number in theframe)=[(numberOfSlotsPerFrame×SFNstart time+slotstarttime)+N×periodicity×numberOfSlotsPerFrame/10]modulo(1024×numberOfSlotsPerFrame)where SFNstart time and slotstart time are the SFN and slot,respectively, of the first transmission of PDSCH where the configureddownlink assignment was (re-)initialized.

In an example, two types of transmission without dynamic grant may beconfigured: configured grant Type 1 where an uplink grant is provided byRRC, and stored as configured uplink grant; and configured grant Type 2where an uplink grant is provided by PDCCH, and stored or cleared asconfigured uplink grant based on L1 signalling indicating configureduplink grant activation or deactivation.

In an example, Type 1 and Type 2 configured grants may be configured byRRC per Serving Cell and per BWP. In an example, multiple configurationsmay be active simultaneously on different Serving Cells. For Type 2configured grant, activation and deactivation may be independent amongthe Serving Cells.

In an example, RRC may configure the following parameters when theconfigured grant Type 1 is configured: cs-RNTI: CS-RNTI forretransmission; periodicity: periodicity of the configured grant Type 1;timeDomainOffset: Offset of a resource with respect to SFN=0 in timedomain; timeDomainAllocation: Allocation of configured uplink grant intime domain which contains startSymbolAndLength; nrofHARQ-Processes: thenumber of HARQ processes for configured grant.

In an example, RRC may configure the following parameters when theconfigured grant Type 2 is configured: cs-RNTI: CS-RNTI for activation,deactivation, and retransmission; periodicity: periodicity of theconfigured grant Type 2; nrofHARQ-Processes: the number of HARQprocesses for configured grant.

In an example, upon configuration of a configured grant Type 1 for aServing Cell by upper layers, the MAC entity may: store the uplink grantprovided by upper layers as a configured uplink grant for the indicatedServing Cell; and initialize or re-initialize the configured uplinkgrant to start in the symbol according to timeDomainOffset and S(derived from SLIV), and to reoccur with periodicity.

In an example, after an uplink grant is configured for a configuredgrant Type 1, the MAC entity may consider that the uplink grant recursassociated with each symbol for which:[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in theslot]=(timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity)modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot),for all N>=0.

In an example, after an uplink grant is configured for a configuredgrant Type 2, the MAC entity may consider that the uplink grant recursassociated with each symbol for which:[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in the slot]=[(SFNstarttime×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstarttime×numberOfSymbolsPerSlot+symbolstarttime)+N×periodicity]modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot),for all N>=0,where SFNstart time, slotstart time, and symbolstart time are the SFN,slot, and symbol, respectively, of the first transmission opportunity ofPUSCH where the configured uplink grant was (re-)initialized.

In an example, when a configured uplink grant is released by upperlayers, all the corresponding configurations may be released and allcorresponding uplink grants shall be cleared.

In an example, if the configured uplink grant confirmation has beentriggered and not cancelled; and if the MAC entity has UL resourcesallocated for new transmission, a MAC entity may instruct theMultiplexing and Assembly procedure to generate an Configured GrantConfirmation MAC CE and cancel the triggered configured uplink grantconfirmation.

In an example, for a configured grant Type 2, the MAC entity may clearthe configured uplink grant in response to a first transmission ofConfigured Grant Confirmation MAC CE triggered by the configured uplinkgrant deactivation. In an example, retransmissions except for repetitionof configured uplink grants may use uplink grants addressed to CS-RNTI.

In an example, a MAC entity may use a Power Headroom reporting procedureto provide a serving base station with the following information: Type 1power headroom: the difference between the nominal UE maximum transmitpower and the estimated power for UL-SCH transmission per activatedServing Cell; Type 2 power headroom: the difference between the nominalUE maximum transmit power and the estimated power for UL-SCH and PUCCHtransmission on SpCell of another MAC entity (e.g., E-UTRA MAC entity inEN-DC case); and Type 3 power headroom: the difference between thenominal UE maximum transmit power and the estimated power for SRStransmission per activated Serving Cell.

In an example, RRC may control Power Headroom reporting by configuringthe following parameters: phr-PeriodicTimer; phr-ProhibitTimer;phr-Tx-PowerFactorChange; phr-Type2OtherCell; phr-ModeOtherCG;multiplePHR.

In an example, a Power Headroom Report (PHR) may be triggered ifphr-ProhibitTimer expires or has expired and the path loss has changedmore than phr-Tx-PowerFactorChange dB for at least one activated ServingCell of any MAC entity which is used as a pathloss reference since thelast transmission of a PHR in this MAC entity when the MAC entity has ULresources for new transmission. In an example, the path loss variationfor one cell assessed above is between the pathloss measured at presenttime on the current pathloss reference and the pathloss measured at thetransmission time of the last transmission of PHR on the pathlossreference in use at that time, irrespective of whether the pathlossreference has changed in between.

In an example, a Power Headroom Report (PHR) may be triggered ifphr-PeriodicTimer expires.

In an example, a Power Headroom Report (PHR) may be triggered uponconfiguration or reconfiguration of the power headroom reportingfunctionality by upper layers, which is not used to disable thefunction.

In an example, a Power Headroom Report (PHR) may be triggered inresponse to activation of an SCell of any MAC entity with configureduplink.

In an example, a Power Headroom Report (PHR) may be triggered inresponse to addition of the PSCell (e.g., if PSCell is newly added orchanged).

In an example, a Power Headroom Report (PHR) may be triggered ifphr-ProhibitTimer expires or has expired, when the MAC entity has ULresources for new transmission, and the following is true for anactivated Serving Cells of any MAC entity with configured uplink: thereare UL resources allocated for transmission or there is a PUCCHtransmission on this cell, and the required power backoff due to powermanagement (e.g., as allowed by P-MPRc) for this cell has changed morethan phr-Tx-PowerFactorChange dB since the last transmission of a PHRwhen the MAC entity had UL resources allocated for transmission or PUCCHtransmission on this cell. In an example, the MAC entity may avoidtriggering a PHR when the required power backoff due to power managementdecreases only temporarily (e.g. for up to a few tens of milliseconds)and it may avoid reflecting such temporary decrease in the values ofPCMAX,f,c/PH when a PHR is triggered by other triggering conditions.

In an example, if the MAC entity has UL resources allocated for a newtransmission and if it is the first UL resource allocated for a newtransmission since the last MAC reset, the MAC entity may startphr-PeriodicTimer.

In an example, if the MAC entity has UL resources allocated for a newtransmission and if the Power Headroom reporting procedure determinesthat at least one PHR has been triggered and not cancelled; and if theallocated UL resources can accommodate the MAC CE for PHR which the MACentity is configured to transmit, plus its subheader, as a result oflogical channel prioritization (LCP) procedure, if multiplePHR withvalue true is configured: for each activated Serving Cell withconfigured uplink associated with a MAC entity, the MAC entity may:obtain the value of the Type 1 or Type 3 power headroom for thecorresponding uplink carrier; if this MAC entity has UL resourcesallocated for transmission on this Serving Cell; or if the other MACentity, if configured, has UL resources allocated for transmission onthis Serving Cell and phr-ModeOtherCG is set to real by upper layers:obtain the value for the corresponding PCMAX,f,c field from the physicallayer.

In an example, if the MAC entity has UL resources allocated for a newtransmission and if the Power Headroom reporting procedure determinesthat at least one PHR has been triggered and not cancelled; and if theallocated UL resources can accommodate the MAC CE for PHR which the MACentity is configured to transmit, plus its subheader, as a result oflogical channel prioritization (LCP) procedure, if multiplePHR withvalue true is configured: if phr-Type2OtherCell with value true isconfigured: if the other MAC entity is E-UTRA MAC entity: obtain thevalue of the Type 2 power headroom for the SpCell of the other MACentity (i.e. S-UTRA MAC entity); the MAC entity may obtain the value ofthe Type 2 power headroom for the SpCell of the other MAC entity (e.g.,E-UTRA MAC entity); and if phr-ModeOtherCG is set to real by upperlayers: the MAC entity may obtain the value for the correspondingPCMAX,f,c field for the SpCell of the other MAC entity (i.e. E-UTRA MACentity) from the physical layer.

In an example, if the MAC entity has UL resources allocated for a newtransmission and if the Power Headroom reporting procedure determinesthat at least one PHR has been triggered and not cancelled; and if theallocated UL resources can accommodate the MAC CE for PHR which the MACentity is configured to transmit, plus its subheader, as a result oflogical channel prioritization (LCP) procedure, if multiplePHR withvalue true is configured: the MAC entity may instruct a Multiplexing andAssembly procedure to generate and transmit the Multiple Entry PHR MACCE based on the values reported by the physical layer.

In an example, if the MAC entity has UL resources allocated for a newtransmission and if the Power Headroom reporting procedure determinesthat at least one PHR has been triggered and not cancelled; and if theallocated UL resources can accommodate the MAC CE for PHR which the MACentity is configured to transmit, plus its subheader, as a result oflogical channel prioritization (LCP) procedure, Single Entry PHR formatmay be used. The MAC entity may obtain the value of the Type 1 powerheadroom from the physical layer for the corresponding uplink carrier ofthe PCell. The MAC entity may instruct the Multiplexing and Assemblyprocedure to generate and transmit the Single Entry PHR MAC CE based onthe values reported by the physical layer.

In an example, if the MAC entity has UL resources allocated for a newtransmission and if the Power Headroom reporting procedure determinesthat at least one PHR has been triggered and not cancelled; and if theallocated UL resources can accommodate the MAC CE for PHR which the MACentity is configured to transmit, plus its subheader, as a result oflogical channel prioritization (LCP) procedure, the MAC entity may startor restart phr-PeriodicTimer; start or restart phr-ProhibitTimer; andcancel all triggered PHR(s).

In example, a Single Entry PHR MAC CE may be identified by a MACsubheader with a corresponding LCID.

The single Entry PHR MA CE may have a fixed size and may consist of twooctets as shown in FIG. 16: R may be a Reserved bit, set to 0; PowerHeadroom (PH) may indicate the power headroom level. The length of thefield may be 6 bits. The reported PH and the corresponding powerheadroom levels are shown in FIG. 17 (the corresponding measured valuesin dB may be pre-configured); PCMAX,f,c may indicate the PCMAX,f,c usedfor calculation of a preceding PH field. The reported PCMAX,f,c and thecorresponding nominal UE transmit power levels are shown in FIG. 18 (thecorresponding measured values in dBm may be pre-configured).

In an example, a Multiple Entry PHR MAC CE may be identified by a MACsubheader with a corresponding LCID.

In an example, a Multiple Entry PHR may have a variable size, and mayinclude a bitmap, a Type 2 PH field and an octet containing theassociated PCMAX,f,c field (if reported) for SpCell of the other MACentity, a Type 1 PH field and an octet containing the associatedPCMAX,f,c field (if reported) for the PCell. It further may include, inascending order based on the ServCellIndex, one or multiple of Type X PHfields and octets containing the associated PCMAX,f,c fields (ifreported) for Serving Cells other than PCell indicated in the bitmap. Xmay be either 1 or 3.

In an example, a presence of Type 2 PH field for SpCell of the other MACentity may be configured by phr-Type2OtherCell with value true.

In an example, a single octet bitmap may be used for indicating thepresence of PH per Serving Cell when the highest ServCellIndex ofServing Cell with configured uplink is less than 8, otherwise fouroctets may be used.

In an example, the MAC entity may determine whether PH value for anactivated Serving Cell is based on real transmission or a referenceformat by considering the configured grant(s) and downlink controlinformation which has been received until and including the PDCCHoccasion in which the first UL grant for a new transmission is receivedsince a PHR has been triggered if the PHR MAC CE is reported on anuplink grant received on the PDCCH or until the first uplink symbol ofPUSCH transmission minus PUSCH preparation time if the PHR MAC CE isreported on a configured grant.

In an example, for a band combination in which the UE does not supportdynamic power sharing, the UE may omit the octets containing PowerHeadroom field and PCMAX,f,c field for Serving Cells in the other MACentity except for the PCell in the other MAC entity and the reportedvalues of Power Headroom and PCMAX,f,c for the PCell may be up to UEimplementation.

In an example, the PHR MAC CEs are defined as follows: Ci may indicatethe presence of a PH field for the Serving Cell with ServCellIndex i.The Ci field set to 1 may indicate that a PH field for the Serving Cellwith ServCellIndex i is reported. The Ci field may be set to 0 and mayindicate that a PH field for the Serving Cell with ServCellIndex i isnot reported; R may be a Reserved bit, set to 0; V may indicate if thePH value is based on a real transmission or a reference format. For Type1 PH, the V field set to 0 may indicate real transmission on PUSCH andthe V field set to 1 may indicate that a PUSCH reference format is used.For Type 2 PH, the V field set to 0 may indicate real transmission onPUCCH and the V field set to 1 may indicate that a PUCCH referenceformat is used. For Type 3 PH, the V field set to 0 may indicate realtransmission on SRS and the V field set to 1 may indicate that an SRSreference format is used. Furthermore, for Type 1, Type 2, and Type 3PH, the V field set to 0 may indicate the presence of the octetcontaining the associated PCMAX,f,c field, and the V field set to 1 mayindicate that the octet containing the associated PCMAX,f,c field isomitted; Power Headroom (PH) may indicate the power headroom level. Thelength of the field may be 6 bits. The reported PH and the correspondingpower headroom levels are shown in FIG. 17 (the corresponding measuredvalues in dB for the NR Serving Cell are pre-configured); P may indicatewhether the MAC entity applies power backoff due to power management (asallowed by P-MPRc). The MAC entity may set the P field to 1 if thecorresponding PCMAX,f,c field would have had a different value if nopower backoff due to power management had been applied; PCMAX,f,c, Ifpresent, may indicate the PCMAX,f,c for the NR Serving Cell and thePCMAX,c or {tilde over (P)}CMAX,c for the E-UTRA Serving Cell used forcalculation of the preceding PH field. The reported PCMAX,f,c and thecorresponding nominal UE transmit power levels are shown in FIG. 18 (thecorresponding measured values in dBm for the NR Serving Cell arepre-configured).

FIG. 19 is an example Multiple Entry PHR MAC CE with the highestServCellIndex of Serving Cell with configured uplink is less than 8.FIG. 20 is an example Multiple Entry PHR MAC CE with the highestServCellIndex of Serving Cell with configured uplink is equal to orhigher than 8.

In an example, the MAC entity may not generate a MAC PDU for the HARQentity if the following conditions are satisfied: the MAC entity isconfigured with skipUplinkTxDynamic with value true and the grantindicated to the HARQ entity was addressed to a C-RNTI, or the grantindicated to the HARQ entity is a configured uplink grant; and there isno aperiodic CSI requested for this PUSCH transmission; and the MAC PDUincludes zero MAC SDUs; and the MAC PDU includes the periodic BSR andthere is no data available for any LCG, or the MAC PDU includes only thepadding BSR.

In an example, an uplink grant for a PDCCH occasion may be received fora Serving Cell on the PDCCH for the MAC entity's CS-RNTI and the NDI inthe received HARQ information may be 1. The MAC entity may consider theNDI for the corresponding HARQ process not to have been toggled. The MACentity may start or restart the configuredGrantTimer for thecorresponding HARQ process, if configured. The MAC entity may deliverthe uplink grant and the associated HARQ information to the HARQ entity.

In an example, an uplink grant for a PDCCH occasion may be received fora Serving Cell on the PDCCH for the MAC entity's CS-RNTI and the NDI inthe received HARQ information may be 0. If PDCCH contents indicateconfigured grant Type 2 deactivation, the MAC entity may triggerconfigured uplink grant confirmation. If PDCCH contents indicateconfigured grant Type 2 activation, the MAC entity may triggerconfigured uplink grant confirmation; the MAC entity may store theuplink grant for this Serving Cell and the associated HARQ informationas configured uplink grant; the MAC entity may initialize orre-initialize the configured uplink grant for this Serving Cell to startin the associated PUSCH duration and to recur according to rules; andthe MAC entity may stop the configuredGrantTimer for the correspondingHARQ process, if running.

In an example, a Configured Grant Confirmation MAC CE may be identifiedby a MAC subheader with a corresponding LCID. The LCID for a ConfiguredGrant Conformation MAC CE may be pre-configured.

In an example, a PDCCH for configured UL grant Type 2 activation,configured UL grant Type 2 release, DL SPS activation and DL SPS releasemay be validated before activation/release of resources. In an example,in response to a CRC of a corresponding DCI format is scrambled with aCS-RNTI provided by the RRC parameter cs-RNTI, and a new data indicatorfield for the enabled transport block is set to ‘0’, a wireless devicemay validate the PDCCH for scheduling activation or scheduling releaseof a DL SPS assignment or configured UL grant Type 2.

In an example, validation of a DCI format may be achieved if fields of aDCI format are set according to pre-defined values. In an example, ifvalidation is achieved, a UE may consider information in the DCI formatas a valid activation or valid release of DL SPS or configured UL grantType 2. If validation is not achieved, the UE may discard theinformation in the DCI format.

In an example, a wireless device may provide HARQ-ACK information inresponse to a SPS PDSCH release after N symbols from the last symbol ofa PDCCH providing the SPS PDSCH release. In an example, N may be basedon wireless device capability. For a first wireless device processingcapability and for the SCS of the PDCCH reception, N=10 for 15 kHz, N=12for 30 kHz, N=22 for 60 kHz, and N=25 for 120 kHz. For a wireless devicewith capability 2 in FR1 and for the SCS of the PDCCH reception, N=5 for15 kHz, N=5.5 for 30 kHz, and N=11 for 60 kHz.

In an example, an IE ConfiguredGrantConfig may be used to configureuplink transmission without dynamic grant according to two possibleschemes. The actual uplink grant may either be configured via RRC(type1) or provided via the PDCCH (addressed to CS-RNTI) (type2).

In an example, a parameter antennaPort may Indicates the antenna port(s)to be used for this configuration. In an example, a parametercg-DMRS-Configuration may indicate DMRS configuration. In an example, aparameter configuredGrantTimer may indicate the initial value of aconfigured grant timer in multiples of periodicity. In an example, aparameter frequencyDomainAllocation may indicate the frequency domainresource allocation. In an example, a parameter dmrs-SeqInitializationmay be configured field if transformPrecoder is disabled. Otherwise thefield may be absent. In an example, an intraSlot value of a parameterfrequencyHopping may indicate enabling of ‘Intra-slot frequency hopping’and a value interSlot may indicate enabling ‘Inter-slot frequencyhopping’. If the field is absent, frequency hopping may not beconfigured. In an example, a parameter frequencyHoppingOffset mayindicate enabling intra-slot frequency hopping with the given frequencyhopping offset. Frequency hopping offset may be used when frequencyhopping is enabled. In an example, a parameter mcs-Table may indicatesthe MCS table the UE may use for PUSCH without transform precoding. Ifthe field is absent the UE may apply the value qam64. In an example, aparameter mcs-TableTransformPrecoder may indicate the MCS table the UEmay use for PUSCH with transform precoding. If the field is absent theUE may apply the value qam64. In an example, a parameter mcsAndTBS mayindicate a modulation order, target code rate and TB size. In anexample, a parameter nrofHARQ-Processes may indicate the number of HARQprocesses configured. It may apply for both Type 1 and Type 2. In anexample, a parameter p0-PUSCH-Alpha may indicate an index of theP0-PUSCH-AlphaSet to be used for this configuration. In an example, aparameter periodicity may indicate a Periodicity for UL transmissionwithout UL grant for type 1 and type 2. In an example,powerControlLoopToUse may indicate closed control loop to apply. In anexample, a parameter repK-RV may indicate the redundancy version (RV)sequence to use. The network may configure this field if repetitions areused, e.g., if repK is set to n2, n4 or n8. Otherwise, the field may beabsent. In an example, a parameter repK may indicate a number ofrepetitions of K. In an example, a parameter resourceAllocation mayindicate Configuration of resource allocation type 0 and resourceallocation type 1. For Type 1 UL data transmission without grant,“resourceAllocation” may be resourceAllocationType0 orresourceAllocationType1. In an example, a parameterrrc-ConfiguredUplinkGrant may indicate configuration for “configuredgrant” transmission with fully RRC-configured UL grant (Type1). If thisfield is absent the UE uses UL grant configured by DCI addressed toCS-RNTI (Type2). In an example, Type 1 configured grant may beconfigured for UL or SUL, but not for both simultaneously. In anexample, a parameter timeDomainAllocation may indicate a combination ofstart symbol and length and PUSCH mapping type. In an example, aparameter transformPrecoder may enable or disable transform precodingfor type1 and type2. If the field is absent, the UE may enable ordisable transform precoding in accordance with the fieldmsg3-transformPrecoder in RACH-ConfigCommon.

In an example, an IE SPS-Config may be used to configure downlinksemi-persistent transmission. Downlink SPS may be configured on theSpCell and/or on SCells. In an example, a parameter mcs-Table mayindicate the MCS table the wireless device may use for DL SPS. Ifpresent, the wireless device may use the MCS table of low-SE 64QAM. Inan example, if this field is absent and field mcs-table in PDSCH-Configis set to ‘qam256’ and the activating DCI is of format 1_1, the UE mayapply the 256QAM table. Otherwise, the UE may apply a non-low-SE 64QAMtable. In an example, a parameter n1PUCCH-AN may indicate HARQ resourcefor PUCCH for DL SPS. The network may configure the resource either asformat0 or format1. The actual PUCCH-Resource may be configured inPUCCH-Config and referred to by its ID.

In an example, a parameter nrofHARQ-Processes may indicate number ofconfigured HARQ processes for SPS DL. In an example, a parameterperiodicity may indicate Periodicity for DL SPS.

A wireless device may be configured with a plurality of uplinkconfigured grant configurations on a cell (e.g., on a BWP of the cell).The plurality of uplink configured grant configurations may comprise afirst uplink configured grant configuration of a first type (e.g., Type1 uplink configured grant configuration) and a second uplink configuredgrant configuration of a second type (e.g. Type 2 uplink configuredgrant). A second plurality of uplink resources may be activated inresponse to receiving configuration parameters of the second uplinkconfigured grant configuration. A first plurality of resources may beactivated in response to the receiving the configuration parameters ofthe first uplink configure grant configuration and a first activationDCI. In an example the first plurality of uplink resources may have afirst periodicity and the second plurality of uplink resources may havea second periodicity. In an example, a first resource of the firstplurality of resources and a second resource of the second plurality ofresources may have overlap in time (e.g., in one or more symbols).Transmission of transport blocks via the first resource and the secondresource may increase wireless device complexity and degrade networkperformance. There is a need to enhance legacy processes when there is aconflict between a first resource of a first Type configured grant and asecond resource of a second type configured grant. Example embodimentsenhance the legacy processes.

In an example embodiment as shown in FIG. 21, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise one or more RRC messages. The one ormore messages may comprise first configuration parameters of a firstconfigured grant configuration on a cell. The one or more messages maycomprise second configuration parameters of a second configured grantconfiguration on the cell. In an example, the first configured grantconfiguration and the second configure grant configuration may be for abandwidth part of the cell. The first configuration parameters of thefirst configured grant may comprise a first periodicity, a first numberof HARQ processes, a first power control parameter, etc. The secondconfiguration parameters of the second configured grant may comprise asecond periodicity, a second number of HARQ processes, a second powercontrol parameter, etc. In an example, the first configured grantconfiguration may be of a first type. In an example, the secondconfigured grant configuration may be of a second type. The first typemay be one of a Type 1 configured grant configuration or Type 2configured grant configuration. The second type may be one of a Type 1configured grant configuration or Type 2 configured grant configuration.

The wireless device may activate a first plurality of resources,associated with the first configured grant configuration, comprising afirst resource. The activation may, based on a first type of the firstconfigured grant configuration, be in response to the receiving thefirst configuration parameters or in response to the receiving the firstconfiguration parameters and a first DCI indicating activation of thefirst configured grant configuration. The wireless device may activate asecond plurality of resources, associated with the second configuredgrant configuration, comprising a second resource. The activation may,based on a second type of the second configured grant configuration, bein response to the receiving the first configuration parameters or inresponse to the receiving the second configuration parameters and asecond DCI indicating activation of the second configured grantconfiguration.

In an example, receiving a Type 1 configured grant configuration mayindicate activation of a plurality of resource. In an example, receivinga Type 2 configured grant configuration and an activation DCI indicatingthe activation of the Type2 configured grant configuration may indicateactivation of a plurality of resources.

The wireless device may determine, as a selected resource, one of thefirst resource associated with the first configured grant configurationand the second resource associated with the second configured grantconfiguration. The first resource and the second resource may overlap inone or more symbols in time.

In an example embodiment as shown in FIG. 22, the determining/selectingthe one of the first resource and the second resource may be based onthe first type of the first configured grant configuration and thesecond type of the second configured grant configuration. The wirelessdevice may transmit a transport block based on a selected resource. Thewireless device may transmit a transport block via the selected resourceand based on a configured grant configuration associated with theselected resource.

In an example, the selected resource may be the first resource,associated with the first configured grant configuration, based on thefirst type of the first configured grant configuration being Type 1 andthe second type of the second configured grant configuration being Type2.

In an example, the selected resource may be the second resource,associated with the second configured grant configuration, based on thefirst type of the first configured grant configuration being Type 1 andthe second type of the second configured grant configuration being Type2.

In an example, the determining/selecting the one of the first resourceand the second resource may be based on the first type of the firstconfigured grant configuration and the second type of the secondconfigured grant configuration and may further be based on a firstservice type associated with the first configured grant configurationand a second service type associated with the second configured grantconfiguration. In an example, the configuration parameters of the firstconfigured grant configuration may indicate the first service type. In aan example, the configuration parameters of the second configured grantconfiguration may indicate the second service type. In an example, theconfiguration parameters of the first configured grant configuration maycomprise one or more first transmission parameters of transport blocksvia resources associated with the first configured grant configuration.The one or more first transmission parameters may indicate the firstservice type. In an example, the configuration parameters of the secondconfigured grant configuration may comprise one or more secondtransmission parameters of transport blocks via resources associatedwith the second configured grant configuration. The one or more secondtransmission parameters may indicate the second service type. In anexample, the first service type may be one of a plurality of servicetypes. In an example, the second service type may be one of a pluralityof service types. The plurality of service types may comprise eMBB,URLLC, etc.

In an example, the determining/selecting the one of the first resourceand the second resource may be based on an activation DCI indicatingactivation of one or more of the first configured grant configurationand the second configured grant configuration. In an example, theactivation DCI may indicate a service type. The determining/selectingmay be based on the service type. In an example, the service type may beURLLC.

In an example, the activation DCI may be associated with a radio networktemporary identifier (RNTI). The determining/selecting may be based onthe RNTI associated with the activation DCI. In an example, the RNTI mayindicate a service type. The determining/selecting may be based on theservice type. In an example, the service type may be URLLC.

In an example embodiment as shown in FIG. 23, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise one or more RRC messages. The one ormore messages may comprise first configuration parameters of a firstconfigured grant configuration on a cell. The one or more messages maycomprise second configuration parameters of a second configured grantconfiguration on the cell. In an example, the first configured grantconfiguration and the second configure grant configuration may be for abandwidth part of the cell. The first configuration parameters of thefirst configured grant may comprise a first periodicity, a first numberof HARQ processes, a first power control parameter, etc. The secondconfiguration parameters of the second configured grant may comprise asecond periodicity, a second number of HARQ processes, a second powercontrol parameter, etc.

The wireless device may receive a first activation DCI. The firstactivation DCI may be associated with a first RNTI. In an example afirst CRC field of the first activation DCI may be scrambled with thefirst RNTI. The first DCI may further be associated with the firstconfigured grant configuration (e.g., may comprise a field indicating afirst identifier of the first configured grant configuration). The firstactivation DCI may indicate activation of a first plurality of resourcesassociated with the first configured grant configuration. The wirelessdevice may activate the first plurality of resources based on thereceiving the first activation DCI.

The wireless device may receive a second activation DCI. The secondactivation DCI may be associated with a second RNTI. In an example asecond CRC field of the second activation DCI may be scrambled with thesecond RNTI. The second DCI may further be associated with second firstconfigured grant configuration (e.g., may comprise a field indicating asecond identifier of the second configured grant configuration). Thesecond activation DCI may indicate activation of a second plurality ofresources associated with the second configured grant configuration. Thewireless device may activate the second plurality of resources based onthe receiving the second activation DCI.

In an example, the first RNTI may indicate a first service type. Thesecond RNTI may indicate a second service type. The wireless device may,based on the service type indicated by an RNTI associated with a DCI,determine logical channels to be included in a transport block, whereinthe transport block is transmitted via a resource activated by the DCI.The service type may indicate the one or more logical channels. In anexample, the first service type may be one of a plurality of servicetypes comprising URLLC, eMBB, etc. The second service type may be one ofa plurality of service types comprising URLLC, eMBB, etc. In an example,there may be a mapping between logical channels and a service type.

The first plurality of resources may comprise a first resource and thesecond plurality of resources may comprise a second resource. The firstresource and the second resource may overlap, e.g., in one or moresymbols. The wireless device may determine/select, as a selectedresource, one of the first resource and the second resource based on thefirst RNTI associate with the first activation DCI and the second RNTIassociated with the second activation DCI. The wireless device maytransmit a transport block via the selected resource. The wirelessdevice may transmit a transport block via the selected resource andbased on configuration parameters of a configured grant associate withthe selected resource.

In an example, the wireless device may select the first resource basedon the first RNTI indicating that the first service type is a first typeof service. In an example, the first type of service may be URLLC.

In an example embodiment as shown in FIG. 24, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise one or more RRC messages. The one ormore messages may comprise first configuration parameters of a firstconfigured grant configuration on a cell. The one or more messages maycomprise second configuration parameters of a second configured grantconfiguration on the cell. In an example, the first configured grantconfiguration and the second configure grant configuration may be for abandwidth part of the cell. The first configuration parameters of thefirst configured grant may comprise a first periodicity, a first numberof HARQ processes, a first power control parameter, etc. The secondconfiguration parameters of the second configured grant may comprise asecond periodicity, a second number of HARQ processes, a second powercontrol parameter, etc. In an example, the first configured grantconfiguration may be of a first type. In an example, the secondconfigured grant configuration may be of a second type. The first typemay be one of a Type 1 configured grant configuration or Type 2configured grant configuration. The second type may be one of a Type 1configured grant configuration or Type 2 configured grant configuration.

The one or more messages may further comprise a priority parameter. Thepriority parameter may indicate a priority of a first type configuredgrant configuration over a second type configured grant configuration.In an example, the priority parameter may indicate priority of a firsttype configured grant over a second type configured grant if one or moreconditions are satisfied. In an example, the one or more conditions maybe based one or more first logical channels and/or service type, whereinthe data of the one or more first logical channels and/or service typeis transmitted via a first resource of the first configured grantconfiguration and one or more second logical channels/service types,wherein data of the one or more second logical channels/service typesare transmitted via a second resource of the second configuredgrantconfiguation.

The wireless device may activate a first plurality of resources,associated with the first configured grant configuration, comprising afirst resource. The activation may, based on a first type of the firstconfigured grant configuration, be in response to the receiving thefirst configuration parameters or in response to the receiving the firstconfiguration parameters and a first DCI indicating activation of thefirst configured grant configuration. The wireless device may activate asecond plurality of resources, associated with the second configuredgrant configuration, comprising a second resource. The activation may,based on a second type of the second configured grant configuration, bein response to the receiving the first configuration parameters or inresponse to the receiving the second configuration parameters and asecond DCI indicating activation of the second configured grantconfiguration.

In an example, receiving a Type 1 configured grant configuration mayindicate activation of a plurality of resource. In an example, receivinga Type 2 configured grant configuration and an activation DCI indicatingthe activation of the Type2 configured grant configuration may indicateactivation of a plurality of resources.

The wireless device may determine, as a selected resource, one of thefirst resource associated with the first configured grant configurationand the second resource associated with the second configured grantconfiguration. The first resource and the second resource may overlap inone or more symbols in time. The determining may be based on thepriority parameter. In an example the determining may be based on thepriority parameter, the first type of the first configured grant and thesecond type of the second configured grant.

In an example, the first type of the first configure grant configurationis one of the Type 1 and Type 2. The second type of the secondconfigured grant configuration is one of the Type 1 and Type 2. In anexample, receiving a type 1 configured grant configuration indicatesactivation of a plurality of resources. In an example, receiving a type2 configured grant configuration and a downlink control indicatesactivation of a plurality of resources. In an example, the first typeconfigured grant configuration is one of a type 1 configured grantconfiguration and a type 2 configured grant configuration. The secondtype configured grant configuration is one of a type 1 configured grantconfiguration and a type 2 configured grant configuration.

A wireless device may be configured with an uplink configured grantconfiguration. The wireless device may receive an activation DCI and inresponse to the receiving the activation DCI, a plurality of uplinkresources, associated with the uplink configured grant configuration,may be activated. The wireless device may or may not transmit based on afirst resource of the plurality resources based on availability of dataor availability of data corresponding to a service type associated withthe uplink configured grant configuration. The wireless device mayreceive a second DCI comprising a second uplink grant indicating asecond resource which has overlap with the first resource. The legacyprocesses for determining power and power headroom report (if triggered)leads to inefficient and degraded network performance for exampleinefficient scheduling by the base station. There is a need to enhancethe legacy power and PHR determination processes in response to conflictbetween dynamic and configured grants. Example embodiments enhance thelegacy power and PHR determination processes in case of conflict betweendynamic and configured grants.

In an example embodiment as shown in FIG. 25, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise RRC messages. The one or more messagesmay comprise configuration parameters of a configured configuration on acell. The configuration parameters may comprise a periodicity parameter,a number of HARQ processes, a power control parameter, etc. In anexample, the wireless device may activate a plurality of resources basedon the configuration parameters of the configured grant configuration.In an example, the wireless device may activate a plurality of resourcesin response to receiving the configuration parameters of the configuredgrant configuration. In an example, the wireless device may activate aplurality of resources in response to receiving the configurationparameters of the configured grant configuration and an activation DCI.

The wireless device may receive a downlink control information (DCI)indicating a first resource of the cell for transmission of a transportblock. The DCI may comprise transmission parameters (e.g., power controlparameters, HARQ related parameters, etc.) for transmission of thetransport block. The first resource, indicated by the DCI, may overlapwith a second resource in the plurality of resources activated based onthe configured grant configuration. In an example, the first resourcemay overlap (e.g., have conflict) with the second resource in one ormore symbols.

The wireless device may determine, as a selected resource. one of thefirst resource (for transmission of the transport block based on theDCI) or the second resource (for transmission of a second transportblock based on the configured grant configuration). The determining theone of the first resource and the second resource may be based on one ormore criteria. The wireless device may transmit a transmission (e.g.,transport block or the second transport block based on the selection)via the selected resource and may drop a transmission (e.g., transportblock or the second transport block based on the selection) based on theunselected resource.

In an example, the transport block may comprise one or more firstlogical channels and the second transport block may comprise one or moresecond logical channels. The determining one of the first resource andthe second resource may be based on the one or more first logicalchannels and the one or more second logical channels. In an example, theDCI may indicate the one or more first logical channels. In an example,the first resource may be associated with a service type and the secondresource may be associated with a second service type. The first servicetype may be one a plurality of service types comprising eMBB, URLLC,etc. In an example, the DCI may indicate the first service type. Thesecond service type may be one a plurality of service types comprisingeMBB, URLLC, etc. The determining one of the first resource and thesecond resource may be based on the first service type and the secondservice type.

In an example embodiment as shown in FIG. 26, the wireless device maydetermine a power headroom report assuming that wireless devicetransmits the transport block based on the DCI regardless of selectingor dropping the transport block. The wireless device may transmit thepower headroom. In an example, the wireless device may multiplex thepower headroom report with the transport block and transmit it via thefirst resource in response to the selecting the first resource. In anexample, the wireless device may multiplex the power headroom reportwith the transport block. The wireless device may receive a second DCIindicating a retransmission grant and may transmit the power headroomreport based on the second DCI in response to selecting the secondresource and dropping the transport block.

In an example, calculating the power headroom report further comprisescalculating one or more power levels of one or more signals. Thewireless device may calculate the power levels assuming that wirelessdevice transmits the transport block based on the DCI regardless ofselecting or dropping the transport block. The wireless device may alsocalculate the one or more power levels assuming that the wireless devicedrops the transport block and use the power levels calculated with thisassumption for transmitting signals in response to the wireless devicedropping the transport block. The wireless device may however calculatethe power headroom report assuming that wireless device transmits thetransport block based on the DCI regardless of selecting or dropping thetransport block.

In an example embodiment as shown in FIG. 27, the wireless device maydetermine a power headroom report assuming that wireless device dropsthe transport block based on the DCI and transmit the second transportblock based on the configured grant configuration regardless ofselecting or dropping the transport block. The wireless device maytransmit the power headroom. In an example, the wireless device maymultiplex the power headroom report with the transport block andtransmit it via the first resource in response to the selecting thefirst resource. In an example, the wireless device may multiplex thepower headroom report with the transport block. The wireless device mayreceive a second DCI indicating a retransmission grant and may transmitthe power headroom report based on the second DCI in response toselecting the second resource and dropping the transport block.

In an example, calculating the power headroom report further comprisescalculating one or more power levels of one or more signals. Thewireless device may calculate the power levels assuming that wirelessdevice drops the transport block based on the DCI and transmit thesecond transport block based on the configured grant configurationregardless of selecting or dropping the transport block. The wirelessdevice may also calculate the one or more power levels assuming that thewireless device transmits the transport block and use the power levelscalculated with this assumption for transmitting signals in response tothe wireless device transmitting the transport block. The wirelessdevice may however calculate the power headroom report assuming thatwireless device drops the transport block based on the DCI and transmitsthe second transport block based on the configured grant configurationregardless of selecting or dropping the transport block.

In an example embodiment as shown in FIG. 28, the wireless device maydetermine a power headroom report assuming that wireless devicetransmits both of the transport block based on the DCI and the secondtransport block based on the configured grant configuration regardlessof selecting or dropping the transport block. The wireless device maytransmit the power headroom. In an example, the wireless device maymultiplex the power headroom report with the transport block andtransmit it via the first resource in response to the selecting thefirst resource. In an example, the wireless device may multiplex thepower headroom report with the transport block. The wireless device mayreceive a second DCI indicating a retransmission grant and may transmitthe power headroom report based on the second DCI in response toselecting the second resource and dropping the transport block.

In an example, calculating the power headroom report further comprisescalculating one or more power levels of one or more signals. Thewireless device may calculate the power levels assuming that wirelessdevice transmits both of the transport block based on the DCI andtransmit the second transport block based on the configured grantconfiguration regardless of selecting or dropping the transport block.The wireless device may also calculate the one or more power levelsassuming that the wireless device transmits the transport block and usethe power levels calculated with this assumption for transmittingsignals in response to the wireless device transmitting the transportblock. The wireless device may also calculate the one or more powerlevels assuming that the wireless device drops the transport block andtransmits the second transport block and use the power levels calculatedwith this assumption for transmitting signals in response to thewireless device dropping the transport block and transmitting the secondtransport block. The wireless device may however calculate the powerheadroom report assuming that wireless device transmits both thetransport block based on the DCI and the second transport block based onthe configured grant configuration regardless of selecting or droppingthe transport block.

In an example embodiment as shown in FIG. 29, the wireless device maydetermine a first power headroom report based on assuming transmittingthe transport block (indicated by the DCI) and dropping the secondtransport block (based on the configured grant configuration). Thewireless device may determine a second power headroom report based onassuming dropping the transport block (indicated by the DCI) andtransmitting the second transport block (based on the configured grantconfiguration). The wireless device may determine the power headroomreport based on the first power headroom report and the second powerheadroom report.

In an example, the determining the power headroom may be based on thefirst power headroom in response to the first power headroom beinglarger than the second power headroom report.

In an example, the determining the power headroom may be based on thefirst power headroom in response to the first power headroom beingsmaller than the second power headroom report.

In an example, the determining the power headroom may be based on thesecond power headroom in response to the first power headroom beinglarger than the second power headroom report.

In an example, the determining the power headroom may be based on thesecond power headroom in response to the first power headroom beingsmaller than the second power headroom report.

The wireless device may transmit the power headroom. In an example, thewireless device may multiplex the power headroom report with thetransport block and transmit it via the first resource in response tothe selecting the first resource. In an example, the wireless device maymultiplex the power headroom report with the transport block. Thewireless device may receive a second DCI indicating a retransmissiongrant and may transmit the power headroom report based on the second DCIin response to selecting the second resource and dropping the transportblock.

In an example, calculating the first power headroom report and thesecond power headroom report further comprises calculating one or morepower levels of one or more signals. To determine the first powerheadroom report, the wireless device may calculate the power levelsassuming that wireless device transmits the transport block based on theDCI and drops the second transport block based on the configured grantconfiguration. To determine the second power headroom report, thewireless device may calculate the power levels assuming that wirelessdevice drops the transport block based on the DCI and transmits thesecond transport block based on the configured grant configuration. Thewireless device may also calculate the one or more power levels assumingthat the wireless device transmits the transport block and use the powerlevels calculated with this assumption for transmitting signals inresponse to the wireless device transmitting the transport block. Thewireless device may also calculate the one or more power levels assumingthat the wireless device drops the transport block and transmits thesecond transport block and use the power levels calculated with thisassumption for transmitting signals in response to the wireless devicedropping the transport block and transmitting the second transportblock.

In an example embodiment as shown in FIG. 30, a wireless device maydetermine the power headroom report based on a minimum processing timecapability. The wireless device may have the capability to determine apower headroom report and multiplex with the transport block fortransmission via the first resource up to a 1^(st) period prior to atiming of the 1^(st) resource. The determining the power headroom may bebased on data arrival for configured grant resource (e.g., secondresource) prior to or after the first period before the timing of thefirst resource.

In an example, the first resource and the second resource may be for abandwidth part of the cell. In an example, the first resource and thesecond resource may have conflict in time domain (e.g., in one or moresymbols). In an example, the first resource and the second resource mayhave conflict in frequency domain (e.g., in one or more resource blocks)

In an example, the wireless device may further transmit a signal of athird resource of a second cell. The third resource may have overlap intime (e.g., in one or more symbols) with the first resource and thesecond resource. The wireless device may determine the power headroomreport based on a power level of the third signal. In an example, thethird signal may be a PUSCH for transmission of a TB. In an example, thethird signal may be PUCCH. In an example, the third signal may be asounding reference signal.

In an example embodiment, a wireless device may receive one or moremessages comprising: first configuration parameters of a firstconfigured grant configuration on a cell; and second configurationparameters of a second configured grant configuration on the cell. Thewireless device may determine/select, as a selected resource, one of: afirst resource associated with the first configured grant configuration;and a second resource associated with the second configured grantconfiguration; wherein: the determining/selecting is based on a firsttype of the first configured grant configuration and a second type ofthe second configured grant configuration; and the first resource andthe second resource overlap in one or more symbols. The wireless devicemay transmit a transport block via the selected resource.

In an example, receiving a type 1 configured grant configuration mayindicate activation of a plurality of resources; and receiving a type 2configured grant configuration and a downlink control, associated withthe type 2 configured grant configuration, may indicate activation of aplurality of resources.

In an example, the selected resource may be the first resource based on:the first type being type 1; and the second type being type 2.

In an example, the selected resource may be the second resource basedon: the first type being type 1; and the second type being type 2.

In an example, the determining may be further based on a first servicetype associated with the first configured grant configuration and asecond service type associated with the second configured grantconfiguration.

In an example, the first service type may be one of a plurality ofservice types comprising URLLC and eMBB; and the second service type maybe one of a plurality of service types comprising URRLC and eMBB.

In an example, the first configuration parameters may indicate the firstservice type; and the second configuration parameters may indicate thesecond service type.

In an example, the determining may be further based on a radio networktemporary identifier (RNTI) associated with the downlink controlinformation. In an example, the RNTI may indicate a first service type.

In an example, the selected resource may be the second resource based onthe RNTI indicating the first service type. In an example, the firstservice type may be URLLC.

In an example, the first configured grant configuration and the secondconfigured grant configuration may be for a bandwidth part of the cell.

In an example embodiment, a wireless device may receive one or moremessages comprising: a first configured grant configuration on a cell;and a second configured grant configuration on the cell. The wirelessdevice may receive a first downlink control information, associated witha first radio network temporary identifier (RNTI) and the firstconfigured grant configuration, indicating activation of a firstplurality of resources. The wireless device may receive a seconddownlink control information, associated with a second RNTI and thesecond configured grant configuration, indicating activation of a secondplurality of resources. The wireless device may determine/select as aselected resource, one of: a first resource in the first plurality ofresources; and a second resource in the second plurality of resources;wherein: the determining/selecting is based on the first RNTI and thesecond RNTI; and the first resource and the second resource overlap inone or more symbols. The wireless device may transmit a transport blockvia the selected resource.

In an example, the first RNTI may indicate a first service type; and thesecond RNTI may indicate a second service type.

In an example, the first service type may be one of a plurality ofservice types comprising URLLC and eMBB; and the second service type maybe one of a plurality of service types comprising URLLC and eMBB.

In an example, the selected resource may be the first resource based onthe first RNTI indicating a first service type. In an example, the firstservice type may be URLLC.

In an example embodiment, a wireless device may receive one or moremessages comprising: a first configured grant configuration on a cell; asecond configured grant configuration on the cell; and a priorityparameter indicating a priority of a first type configured grantconfiguration over a second type configured grant configuration. Thewireless device may determine/select, as a selected resource, one of afirst resource associated with the first configured grant configuration;and a second resource associated with the second configured grantconfiguration; wherein: the determining/selecting is based on a firsttype of the first configured grant configuration, a second type of thesecond configured grant configuration and the priority parameter; andthe first resource and the second resource overlap in one or moresymbols. The wireless device may transmit a transport block via theselected resource.

In an example, the first type of the first configured grantconfiguration may be one of a type 1 and type 2; and the second type ofthe second configured grant configuration may be one of a type 1 andtype 2.

In an example, receiving a type 1 configured grant configuration mayindicate activation of a plurality of resources; and receiving a type 2configured grant configuration and a downlink control may indicateactivation of a plurality of resources.

In an example, the first type configured grant configuration may be oneof a type 1 configured grant configuration and a type 2 configured grantconfiguration; and the second type configured grant configuration may beone of a type 1 configured grant configuration and a type 2 configuredgrant configuration.

In an example embodiment, a wireless device may receive configurationparameters of a configured grant configuration on a cell. The wirelessdevice may receive a downlink control information indicating a firstresource of the cell for transmission of a transport block, wherein thefirst resource overlaps/has conflict with a second resource associatedwith the configured grant configuration. The wireless device maydetermine a power headroom report assuming that the wireless devicetransmits the transport block regardless of transmitting or dropping thetransport block. The wireless device may transmit the power headroomreport.

In an example, the wireless device may calculate a transmission power ofthe transport block assuming that the wireless device transmits thetransport block regardless of transmitting or dropping the transportblock.

In an example embodiment, a wireless device may receive configurationparameters of a configured grant configuration on a cell. The wirelessdevice may receive a downlink control information indicating a firstresource of the cell for transmission of a transport block, wherein thefirst resource overlaps/has conflict with a second resource associatedwith the configured grant configuration. The wireless device maydetermine a power headroom report based on the transmission of thetransport block. The wireless device may drop the transport block basedon the first resource overlapping/having conflict with a second resourceassociated with the configured grant configuration. The wireless devicemay transmit the power headroom report.

In an example embodiment, a wireless device may receive configurationparameters of a configured grant configuration on a cell. The wirelessdevice may receive a downlink control information indicating a firstresource of the cell for transmission of a transport block, wherein thefirst resource overlaps/has conflict with a second resource associatedwith the configured grant configuration. The wireless device maydetermine a power headroom report assuming that the wireless devicedrops the transport block regardless of transmitting or dropping thetransport block. The wireless device may transmit the power headroomreport.

In an example, the wireless device may calculate a transmission power ofa second transport block, for transmission via the second resource,assuming that the wireless device drops the transport block regardlessof transmitting or dropping the transport block.

In an example embodiment, a wireless device may receive configurationparameters of a configured grant configuration on a cell. The wirelessdevice may receive a downlink control information indicating a firstresource of the cell for transmission of a transport block, wherein thefirst resource overlaps/has conflict with a second resource associatedwith the configured grant configuration. The wireless device maydetermine a power headroom report based on dropping the transport blockand transmitting a second transport block via the second resource. Thewireless device may transmit the transport block via the first resource.The wireless device may transmit the power headroom report.

In an example embodiment, a wireless device may receive configurationparameters of a configured grant configuration on a cell. The wirelessdevice may receive a downlink control information indicating a firstresource of the cell for transmission of a transport block, wherein thefirst resource overlaps/has conflict with a second resource associatedwith the configured grant configuration. The wireless device maydetermine a power headroom report assuming that the wireless devicetransmits both of the transport block and a transmission via the secondresources. The wireless device may transmit the power headroom report.

In an example, the wireless device may calculate a transmission power ofthe transport block and a second transport block, for transmission viathe second resource, assuming that the wireless device transmits boththe transport block and the second transport block.

In an example embodiment, a wireless device may receive configurationparameters of a configured grant configuration on a cell. The wirelessdevice may receive a downlink control information indicating a firstresource of the cell for transmission of a transport block, wherein thefirst resource overlaps/has conflict with a second resource associatedwith the configured grant configuration. The wireless device may select,as a selected transport block, one of the transport block and the secondtransport block. The wireless device may transmit the selected transportblock. The wireless device may transmit the power headroom report.

In an example embodiment, a wireless device may receive configurationparameters of a configured grant configuration on a cell. The wirelessdevice may receive a downlink control information indicating a firstresource of the cell for transmission of a transport block, wherein thefirst resource overlaps/has conflict with a second resource associatedwith the configured grant configuration. The wireless device maydetermine a first power headroom based on transmitting the transportblock and dropping a second transport block for transmission via thesecond resource. The wireless device may determine a second powerheadroom based on dropping the transport block and transmitting thesecond transport block for transmission via the second resource. Thewireless device may determine a power headroom report based on the firstpower headroom and the second power headroom. The wireless device maytransmit the power headroom report.

In an example, the determining the power headroom report may be based onthe first power headroom report in response to the first power headroombeing larger than the second power headroom.

In an example, the determining the power headroom report may be based onthe first power headroom in response to the first power headroom beingsmaller than the second power headroom.

In an example, the determining the power headroom report may be based onthe second power headroom in response to the first power headroom beinglarger than the second power headroom.

In an example, the second power headroom in response to the first powerheadroom being smaller than the second power headroom.

In an example, the wireless device may select one of the transport blockand a second transport block for transmission via the second resource,based on one or more criteria.

In an example, the transport block comprises one or more first logicalchannels; the second transport block comprises one or more secondlogical channels; and the selecting is based on the one or more firstlogical channels and the one or more second logical channels. In anexample, the downlink control information indicates the one or morefirst logical channels.

In an example, the transport block comprises the power headroom report.In an example, the transport block further comprises one or more firstlogical channels.

In an example, the wireless device may select the transport block fortransmission via the first resource. The wireless device may transmitthe transport block via the first resource. The wireless device may dropa second transport block for transmission via the second resource.

In an example, the wireless device may select a second transport blockfor transmission via the second resource. The wireless device may dropthe transport block. The wireless device may receive a second downlinkcontrol information indicating retransmission of the transport block.The wireless device may transmit the transport block based on the seconddownlink control information.

In an example, the first resource and the second resource may be for abandwidth part of the cell.

In an example, the first resource and the second resource may haveconflict in time-domain.

In an example, the first resource and the second resource may overlap inone or more symbols.

In an example, the first resource and the second resource have conflictin frequency-domain.

In an example, the wireless device may transmit a signal via a thirdresource of a second cell, wherein the third resource overlaps with thefirst resource and the second resource in time. In an example, the thirdsignal may be a third transport block. In an example, the third signalmay be transmitted via a physical uplink control channel. In an example,the third signal may be a sounding reference signal.

In an example embodiment, a wireless device may receive configurationparameters of a configured grant configuration on a cell. The wirelessdevice may receive a first downlink control information indicating afirst resource of the cell for transmission of a transport block,wherein: the first resource overlaps/has conflict with a second resourceassociated with the configured grant configuration; and the transportblock is associated with a HARQ process. The wireless device may select,as a selected resource, one of the transport block and a secondtransport block for transmission via the second resource. The wirelessdevice may transmit one of the transport block or the second transportblock via the selected resource, wherein the transmitting fails. Thewireless device may receive a second downlink control informationindicating a transmission corresponding to the HRQ process. The wirelessdevice may consider a new data indicator field of the second downlinkcontrol information not being toggled regardless of a value of the newdata indicator field.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 31 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 3110, a wireless device may receive one ormore radio resource control (RRC) messages by a base station. The RRCmessages may comprise configuration parameters of a cell. Theconfiguration parameters may comprise first parameters of a firstconfigured grant configuration of the cell and second parameters of asecond configured grant configuration of the cell. At 3120, the wirelessdevice may trigger a power headroom report. At 3130, the wireless devicemay determine, as a selected uplink resource for transmitting the powerheadroom report, based on a first priority of the first configured grantconfiguration and a second priority of the second configured grantconfiguration, one of: a first resource associated with the firstconfigured grant configuration; and a second resource associated withthe second configured grant configuration. The first resource and thesecond resource may overlap in one or more symbols. At 3140, thewireless device may transmit the power headroom report via the selecteduplink resource.

According to an example embodiment, the wireless device may determine afirst power headroom value of the cell based on the selected uplinkresource. The power headroom report may comprise the first powerheadroom value of the cell. The wireless device may determine a secondpower headroom value of the cell based on a resource of the firstresource and the second resource, wherein the resource is not theselected uplink resource based on the determining. The power headroomreport further comprises the second power headroom value of the cell.The power headroom report does not comprise the second power headroomvalue of the cell.

According to an example embodiment, the wireless device may determinethe first priority of the first configured grant configuration based onone or more first logical channels configured to be mapped to the firstconfigured grant configuration. The wireless device may determine thesecond priority of the second configured grant configuration based onone or more second logical channels configured to be mapped to thesecond configured grant configuration. For example, the first priorityis a highest logical channel index among the one or more first logicalchannels. For example, the first priority is a lowest logical channelindex among the one or more first logical channels. For example, thesecond priority is a highest logical channel index among the one or moresecond logical channels. For example, the second priority is a lowestlogical channel index among the one or more second logical channels.

According to an example embodiment, the wireless device may furtherdetermine the selected uplink resource based on a first service typeassociated with the first configured grant configuration; and a secondservice type associated with the second configured grant configuration.The first service type may be one of a plurality of service typescomprising ultra-reliable and low latency communication (URLLC) andenhanced mobile broadband (eMBB). The second service type may be one ofthe plurality of service types comprising URLLC and eMBB. The firstconfiguration parameters may indicate the first service type. The secondconfiguration parameters may indicate the second service type. Forexample, the first service type may be URLLC. For example, second firstservice type may be eMBB.

According to an example embodiment, the wireless device may furtherdetermine the selected uplink resource based on a radio networktemporary identifier (RNTI) associated with a downlink controlinformation. For example, the RNTI may indicate a first service type.The selected uplink resource may be the second resource based on theRNTI indicating the first service type.

According to an example embodiment, the first type may be URLLC. Thefirst configured grant configuration and the second configuration grantconfigurations may be configured for a bandwidth part of the cell. Forexample, the power headroom report may comprise an allowed power of thecell.

According to an example embodiment, a wireless device may receive one ormore messages comprising first parameters of a first configured grantconfiguration of a cell; and a downlink control information (DCI)comprising a second priority and resource assignments for a secondresource. The wireless device may trigger a power headroom report. Thewireless device may determine, as a selected uplink resource fortransmitting the power headroom report, one of: a first resourceassociated with the first configured grant configuration; and the secondresource, wherein the first resource and the second resource overlap inone or more symbols. The wireless device may further determine theselected uplink resource based on a first priority of the firstconfigured grant configuration and the second priority indicated in theDCI. The wireless device may transmit the power headroom report via theselected uplink resource.

According to an example embodiment, a wireless device may receive one ormore radio resource control (RRC) messages comprising configurationparameters for a cell. The configuration parameters may comprise firstconfiguration parameters of a first configured grant configuration onthe cell. The configuration parameters may comprise second configurationparameters of a second configured grant configuration on the cell. Thewireless device may determine, as a selected resource, one of: a firstresource associated with the first configured grant configuration; and asecond resource associated with the second configured grantconfiguration. The wireless device may determine the selected resourcebased on a first type of the first configured grant configuration and asecond type of the second configured grant configuration. The firstresource and the resource may overlap in one or more OFDM symbols. Thewireless device may transmit a transport block via the selectedresource.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of base stations or a plurality ofwireless devices in a coverage area that may not comply with thedisclosed methods, for example, because those wireless devices or basestations perform based on older releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more (or at leastone) message(s) comprise a plurality of parameters, it implies that aparameter in the plurality of parameters is in at least one of the oneor more messages, but does not have to be in each of the one or moremessages. In an example embodiment, when one or more (or at least one)message(s) indicate a value, event and/or condition, it implies that thevalue, event and/or condition is indicated by at least one of the one ormore messages, but does not have to be indicated by each of the one ormore messages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (i.e.hardware with a biological element) or a combination thereof, all ofwhich may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device. Theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

The invention claimed is:
 1. A method comprising: receiving, by awireless device, one or more messages comprising: first parameters of afirst configured grant configuration of an uplink carrier of a cell; andsecond parameters of a second configured grant configuration of theuplink carrier of the cell; triggering a power headroom report;determining as a selected uplink resource for transmitting the powerheadroom report, based on a first priority of the first configured grantconfiguration and a second priority of the second configured grantconfiguration, one of: a first resource associated with the firstconfigured grant configuration; and a second resource associated withthe second configured grant configuration, wherein the first resourceand the second resource overlap in one or more symbols; and transmittingthe power headroom report via the selected uplink resource.
 2. Themethod of claim 1, further comprising determining a first power headroomvalue of the uplink carrier of the cell based on the selected uplinkresource.
 3. The method of claim 2, wherein the power headroom reportcomprises the first power headroom value of the uplink carrier of thecell.
 4. The method of claim 3, further comprising determining a secondpower headroom value of the uplink carrier of the cell based on: aresource of the first resource and the second resource, wherein theresource is not the selected uplink resource.
 5. The method of claim 4,wherein the power headroom report further comprises the second powerheadroom value of the uplink carrier of the cell.
 6. The method of claim4, wherein the power headroom report does not comprise the second powerheadroom value of the uplink carrier of the cell.
 7. The method of claim1, further comprising determining the first priority of the firstconfigured grant configuration based on one or more first logicalchannels configured to be mapped to the first configured grantconfiguration.
 8. The method of claim 7, further comprising determiningthe second priority of the second configured grant configuration basedon one or more second logical channels configured to be mapped to thesecond configured grant configuration.
 9. The method of claim 8, whereinthe first priority is a highest logical channel index among the one ormore first logical channels.
 10. The method of claim 9, wherein thesecond priority is a highest logical channel index among the one or moresecond logical channels.
 11. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive one ormore messages comprising: first parameters of a first configured grantconfiguration of an uplink carrier of a cell; and second parameters of asecond configured grant configuration of the uplink carrier of the cell;trigger a power headroom report; determine as a selected uplink resourcefor transmitting the power headroom report, based on a first priority ofthe first configured grant configuration and a second priority of thesecond configured grant configuration, one of: a first resourceassociated with the first configured grant configuration; and a secondresource associated with the second configured grant configuration,wherein the first resource and the second resource overlap in one ormore symbols; and transmit the power headroom report via the selecteduplink resource.
 12. The wireless device of claim 11, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to determine a first power headroom value of theuplink carrier of the cell based on the selected uplink resource. 13.The wireless device of claim 12, wherein the power headroom reportcomprises the first power headroom value of the uplink carrier of thecell.
 14. The wireless device of claim 13, wherein the instructions,when executed by the one or more processors, further cause the wirelessdevice to determine a second power headroom value of the uplink carrierof the cell based on: a resource of the first resource and the secondresource, wherein the resource is not the selected uplink resource. 15.The wireless device of claim 14, wherein the power headroom reportfurther comprises the second power headroom value of the uplink carrierof the cell.
 16. The wireless device of claim 14, wherein the powerheadroom report does not comprise the second power headroom value of theuplink carrier of the cell.
 17. The wireless device of claim 11, whereinthe instructions, when executed by the one or more processors, furthercause the wireless device to determine the first priority of the firstconfigured grant configuration based on one or more first logicalchannels configured to be mapped to the first configured grantconfiguration.
 18. The wireless device of claim 17, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to determine the second priority of the secondconfigured grant configuration based on one or more second logicalchannels configured to be mapped to the second configured grantconfiguration.
 19. The wireless device of claim 18, wherein the firstpriority is a highest logical channel index among the one or more firstlogical channels.
 20. A system comprising: a base station; and awireless device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: receive one or more messages comprising: firstparameters of a first configured grant configuration of an uplinkcarrier of a cell; and second parameters of a second configured grantconfiguration of the uplink carrier of the cell; trigger a powerheadroom report; determine as a selected uplink resource fortransmitting the power headroom report, based on a first priority of thefirst configured grant configuration and a second priority of the secondconfigured grant configuration, one of: a first resource associated withthe first configured grant configuration; and a second resourceassociated with the second configured grant configuration, wherein thefirst resource and the second resource overlap in one or more symbols;and transmit the power headroom report via the selected uplink resource.